How could I show performance issues on other servers compared to load test results

I have some Unix machines that we need to monitor performance on while we run our load tests. Is there a good methodology on how this should be done?
Thanks- Claucher
=======================================================
Hi CLaucher

There's no support to collect Unix/Linux performace information in the Visual Studio load test. I wish I had a more helpful reply.
-Bill.Wang(MSFT)
=======================================================
Hi CLaucher,

I am guesing your database residing on those unix/linux servers. In this case, you can run some unix commands(performance related) on those unix machines to monitor the performance. You can tell DBA who administer those severs to send you the performance matrix(by unix command) during the period of ur load test.

I hope it helps.
Thanks -- Jaeed
=========================================================

VSTestHost.exe uses only one CPU

I recently noticed that while running a load test, VStestHost.exe uses only one CPU. Trying to change the affinity through task manager has no effect and it continues to run on CPU0. Is that expected behavior or there's something wrong in the way I am executing the load.
==============================================================================
Hi Pawan,

This is by design in Visual Studio 2008. To drive additoinal load, and utilize all CPUs, you need the Test Load Agent / Controller to create your test rig.

Robert
==============================================================================
Thanks George,

so what it indirectly means is that I'll have to procure additional licenses for Load Agent and Controller.
Just wondering if both of em are shipped as part of the MSDN subscription?

Pawan

==============================================================================
Hi Pawan,

Each Load Agent license covers a controller, so the controller is part of the Load Agent purchase. For MSDN, they have a trial version, but be warned its double time bombed - I think its 60-days or 25 test runs, whichever comes first.

Robert