User talk:Peak: Difference between revisions

From Rosetta Code
Content added Content deleted
(my thoughts on timing)
(Detail in timings.)
Line 6: Line 6:
1.223 1.181
1.223 1.181
:-- [[User:Eriksiers|Erik Siers]] ([[User talk:Eriksiers|talk]]) 22:44, 28 September 2014 (UTC)
:-- [[User:Eriksiers|Erik Siers]] ([[User talk:Eriksiers|talk]]) 22:44, 28 September 2014 (UTC)

::Hi Erik, that's good too, but again it is hard for others to make much of such timings: is a 10% difference truly significant or reproducible by others for example? With those timings I am likely to state that timings are comparable and no more. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 09:26, 28 April 2015 (UTC)

Revision as of 09:26, 28 April 2015

Hi Peak, and welcome to RC. Thanks for your contributions so far, but I would just say that we tend to omit timings on RC or restrict them to orders_of_magnitude comparisons or use woolly terms such as "roughly 100 times faster than", or "" time for a coffee". The reason is if conditions are stated to make more accurate times reproducible then that information would obscure the comparison of other aspects of the language and, from other sites, it just isn't easy to do. In short, I, as a long term RC user, tend to very rarely quote timings. Thanks, --Paddy3118 (talk) 06:32, 20 September 2014 (UTC)

I can't recall if I've ever done so here on RC, but when I've had to do that sort of thing elsewhere, I tend to include a before-and-after comparison from my machine, demonstrating the difference, rather than saying "X will be so many milliseconds faster" or whatever, e.g.:
before  after
1.234   1.111
1.251   1.059
1.223   1.181
-- Erik Siers (talk) 22:44, 28 September 2014 (UTC)
Hi Erik, that's good too, but again it is hard for others to make much of such timings: is a 10% difference truly significant or reproducible by others for example? With those timings I am likely to state that timings are comparable and no more. --Paddy3118 (talk) 09:26, 28 April 2015 (UTC)