On Wed, Jun 24, 2009 at 11:45 AM, Rodger Donaldson<rod...@diaspora.gen.nz> wrote:
> Obviously profiling tools are subject to the usual caveats re: accuracy > of reporting in a virtualised environment, but these are a good starting > point. When I looked at jinsight it assumed wall clock time is CPU resources spent. For us that only holds when you have infinite CPU resources available or you would be barking up the wrong tree. In this particular case that means get back to one virtual CPU for the Linux guests, at least for the sake of understanding where the cycles go. After all, we don't expect the number of virtual CPUs to make a difference in what task uses how much CPU cycles, just how much elapsed time it takes to consume that. -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
