On Fri, 23 Dec 2011, Alexandre Bergel wrote:
Hi!MessageTally seems to give wrong values regarding the relative time spent. Consider: MessageTally spyOn: [ 100 timesRepeat: [ 1000 factorial ] ] It gives something like: -=-=-=-=-=-=-=-=-=-=-=-= - 377 tallies, 379 msec. **Tree** -------------------------------- Process: (40s) 464519168: nil -------------------------------- 65.8% {249ms} SmallInteger(Integer)>>factorial 65.8% {249ms} SmallInteger(Integer)>>factorial 65.8% {249ms} SmallInteger(Integer)>>factorial 65.8% {249ms} SmallInteger(Integer)>>factorial ... -=-=-=-=-=-=-=-=-=-=-=-= I would expect to have 100% at the root of the call graph since other threads are not reported. Is there something I am missing? If no, then I will dive into MessageTally. This is annoying.
This means that some other process (probably the finalization process, since #factorial creates a lot of garbage) was running and/or gc happened during the "missing" 34.2%. The gc times are listed below.
Levente
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
