The context is monitoring the performance of a *web application* deployed on a Linux machine.
Currently, our software monitors CPU utilization and memory (% available). We are going to add monitoring of more detailed stats, such as: - context switches/sec - page reads and writes/sec - packets received and sent/sec - packet send errors/sec - collisions/sec (is this even relevant for modern network architectures?) - disk reads and writes/sec These are all relatively easy to get via /proc/stat, /proc/meminfo and /proc/net/dev. What else would a network/linux admin look at to help the testers and developers locate performance bottlenecks? TIA, Chris -- ------------------------------------------------------------------------ - Chris Merrill | Web Performance, Inc. [EMAIL PROTECTED] | http://webperformance.com 919-433-1762 | 919-845-7601 Website Load Testing and Stress Testing Software & Services ------------------------------------------------------------------------ - -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
