using "top" linux semi-permanent instrumentation


i'm perplexing best proceed 'top' semi-permanent orchestration growth box controlling embedded linux. (the orchestration private final-test prolongation releases.)



my initial pass simply supplement init.d:



top -b -d 15 >/tmp/toploop.out &


this runs tip "batch" mode each 15 seconds. let's assume /tmp excess space



questions:




  1. is 15 seconds good value select general-purpose monitoring?

  2. other hoop space, extremely perturbing state system?

  3. what (perhaps better) collection used this?



Comments

Popular posts from this blog

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?

grails record upload problems

how i emanate permitted url asp.net mvc?