Posted on February 7, 2016, 8:31 pm by Dan
1. Classification
Before getting into action, let’s split the “performance” problem in a couple of boxes, as the concept itself is quite general. First, deciding what we want to monitor (an entire system? a particular application?) – and second, deciding on what type of performance monitoring do we require (stats collection by the kernel? in-depth analysis?). Based on this particular classification, we may end up with 4 categories, each with its particular software selection:
Stats (Counters) | Tracing / Profiling / Debugging | |
System Wide | ||
Per Process |
NB:
netstat offers much more info beyond statistics on interface / protocol and may also be used to monitor individual connections.
dtrace and SystemTap can also trace individual applications.
No comments yet Categories: Monitoring, Scripts Tags: file system, linux, memory, performance, script, tracing