On 6/20/06, Tom Duerbusch <[EMAIL PROTECTED]> wrote:
However, in one of the directories, there is a log with the output of a series of performance related commands. i.e. something like "top" being executed every minute and the output captured. (This is under SUSE.) If you find those logs, you might be able to find out the system state during your FTP. Or just try the FTP again while watching "vmstat 10 100" (every 10 seconds for 100 occurrances).
Be careful though that your ad-hoc instrumentation is not going to cause load itself. Unless you validated the cost of it, you can not be sure you're not causing it to swap for example. If you just care about swapping: when you swap to VDISK the I/O rate to VDISK for that virtual machine is reported by the monitor, so you can tell what the swap rate was without looking inside... But quite often you also want to see other things (e.g. CPU usage, network traffic, fragmentation, etc). That's why we consolidate Linux measurements in a performance database for review and reporting. And the neat thing is that I can go and look at what happened during the test, without having to set up my instrumentation and run the test again. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
