Curve fitting for numerical parameter

[GoogleCodeExporter]

Caliper should support an estimate of complexity in Big O notation.  Maybe done 
through a particular runner, caliper could display what it guesses the 
performance of your algorithm will be e.g.

O(1)
O(N)
O(N^2)

It could do this by looking using a parameter of size of the dataset instead of 
just number of repetitions.

Original issue reported on code.google.com by yuri.sch...@gmail.com on 24 Feb 2011 at 9:05

[GoogleCodeExporter]

More generally, it would do Curve Fitting.
http://en.wikipedia.org/wiki/Curve_fitting

The first step would be allowing the user to declare which numerical parameters 
make sense to use as an X axis for such a curve. If we did that, it would then 
be useful to actually draw those graphs in the web results. The obvious next 
step would be curve fitting.

Original comment by kevinb@google.com on 24 Feb 2011 at 3:15

• Changed title: Curve fitting for numerical parameter
• Changed state: Accepted

[GoogleCodeExporter]

Original comment by kevinb@google.com on 19 Mar 2011 at 2:13

• Added labels: Milestone-Post-1.0

[GoogleCodeExporter]

Original comment by kevinb@google.com on 19 Mar 2011 at 3:06

• Added labels: Type-Enhancement

[GoogleCodeExporter]

Original comment by kevinb@google.com on 8 Feb 2012 at 9:46

• Added labels: Component-WebUI

[GoogleCodeExporter]

Original comment by kevinb@google.com on 1 Nov 2012 at 8:32