Re: [Pharo-project] ECompletion/OCompletion tests takes A LIFE!!
Sept. 29, 2010
8:41 a.m.
On
30k was a bit optimistic assumption. For example the Pharo 1.1 OneClick image has 3220 globals. The sortBlock asks for the preference twice per evaluation. SortedCollection uses a binary search during #add:. If we are optimistic, then the preference is asked 3220 * (3220 ln / 2 ln) * 2 times which is ~75k.
In the same image the "old" code asked for the preference 2282899 times during the tests, while the new code did it only 398 times. If the preference is changed to return the value of a variable, then the difference is only 80 ms, otherwise it's 36.6 seconds.
As you see we got trap in a tempest of documents to write :) so do not forget to open bug entry wehn some actions should be taken.... Soon back to life Stef
5784
Age (days ago)
5784
Last active (days ago)
0 comments
1 participants
participants (1)
-
Stéphane Ducasse