Same tests on latest build (0.4.0-dev+5468): tf1 (vectorized): 0.00457 seconds tf2 (loop): 0.00805 seconds tf3 (comprehension): 0.00197 seconds tf4 (map): 0.04186 seconds
I have to say the progression in the performance department is exciting -- improvements in all fronts! Yet, relatively (I guess this is almost nitpicking), comprehension is still faster than others. I did suspected GC to be the cause. But I feel I lack the knowledge to properly analyse its behaviour with @time(d) macro. I did note notice, however, the standard deviations for the seconds used are vastly different: tf1 (vectorized): 0.0000976434 seconds tf2 (loop): 0.0009162303 seconds tf3 (comprehension): 0.0001677752 seconds tf4 (map): 0.0020671911 seconds Maybe the variations are related to GC behaviours? On Saturday, 20 June 2015 20:24:47 UTC+1, Scott Jones wrote: > > Also, you might want to retry your tests on 0.4 (if you don't mind living > on the bleeding edge!), there've been a number of changes there that would > affect your results. > On Saturday, 20 June 2015 20:24:47 UTC+1, Scott Jones wrote: > > Also, you might want to retry your tests on 0.4 (if you don't mind living > on the bleeding edge!), there've been a number of changes there that would > affect your results. >
