From d90d32225055ddca40bc550e9c9eafefd155a3b7 Mon Sep 17 00:00:00 2001 From: Egor Tensin Date: Wed, 9 Mar 2016 01:28:19 +0300 Subject: plots: update --- plots.html | 36 ++++++++++++++++++++++++++++++++---- 1 file changed, 32 insertions(+), 4 deletions(-) (limited to 'plots.html') diff --git a/plots.html b/plots.html index 58ca1d9..6f50123 100644 --- a/plots.html +++ b/plots.html @@ -117,9 +117,21 @@ plots: ---

Plots

-

The platform under which the plots were produced was:

- - +
+
+

The goals of this "project" include a) familiarizing +myself with a few sorting algorithms by examining their (possibly, simplified) +implementations and b) studying the way algorithm's running time changes in +relation to the length of its input (a.k.a. identifying its time +complexity).

+

A simple way to visualize the way algorithm's running +time changes would be to make appropriate measurements and plot them on a nice +graph. +The results of course are highly dependent on the hardware used, while the +graph's look depends on the software used for rendering.

+

Both the hardware & the software that were used to +produce the plots are listed below.

+
@@ -137,10 +149,26 @@ plots:
CPU Intel Atom N28001.4.0
+ + {% if page.plots and page.plots != empty %}
+

The table & plots below are just an attempt to nicely lay out the +data generated using the code from the project repository's master +branch. +Visit https://github.com/egor-tensin/sorting_algorithms/ for more details.

+ +

In short, each of the implemented algorithms was provided with three +input sequences:

+
    +
  • a list of n consecutive numbers sorted in ascending order ("sorted" input),
  • +
  • … in descending order ("reversed" input),
  • +
  • … in random order ("randomized" input).
  • +
+

Use the table below to quickly navigate to the plots for the +corresponding algorithm.

@@ -195,6 +223,6 @@ plots: {% endfor %} {% else %} -

Sorry, there're no plots yet.

+

Sorry, not plots have been added yet.


{% endif %} -- cgit v1.2.3