By wombat42a
via savvyduck.blogspot.com
Published: Jun 09 2008 / 20:14
Getting performance or timing information about an operation in a multithreaded Java application has always been a challenge. The problem has been that most stopwatch functions accounted for the time that the thread took to execute, but included time from other threads executing in parallel in the background. These other threads cause your thread to yield for a period and thus skew your performance statistics. The way around it was to use a performance tool that could track the other threads and calculate an approximation of how long your thread actually took to execute.
Add your comment