Hi Derek,
I just asked Andreas about it. The question is a bit complicated, and doesn't have a single answer. There are two major issues:
1) the time consumed by long-running primitives is incorrectly assigned to the next message send.
2) if you have a large number of processes that wake up with a timer interrupt, perform a sub-millisecond action, and then sleep (for instance, on a heavily loaded Croquet router) then the results will be statistically biased, because the same interrupt that wakes up the profiler also wakes up the sleeping process.
An example of 1) can be seen in:
What is your target hardware? What are your scenes like (#vertices/#objects)?
Josh
On Apr 4, 2008, at 11:44 AM, Derek Arndt wrote:
Hey guys,
I'm back again investigating rendering and general performance of croquet (especially on low end machines where the UMNs Spanish Language Project it's unplayable), when I ran into this e-mail: https://lists.duke.edu/sympa/arc/croquet-dev/2007-10/msg00071.html
What's the status of MessageTally, is it still deemed unreliable?
Cheers,
Derek
