On Tue, Feb 26, 2013 at 2:30 PM, Jeff Janes <jeff.janes@xxxxxxxxx> wrote: > On Fri, Feb 15, 2013 at 10:52 AM, Scott Marlowe <scott.marlowe@xxxxxxxxx> > wrote: >> >> On Fri, Feb 15, 2013 at 11:26 AM, Josh Berkus <josh@xxxxxxxxxxxx> wrote: >> > On 02/14/2013 08:47 PM, Scott Marlowe wrote: >> >> If you run your benchmarks for more than a few minutes I highly >> >> recommend enabling sysstat service data collection, then you can look >> >> at it after the fact with sar. VERY useful stuff both for >> >> benchmarking and post mortem on live servers. >> > >> > Well, background sar, by default on Linux, only collects every 30min. >> > For a benchmark run, you want to generate your own sar file, for >> > example: >> >> On all my machines (debian and ubuntu) it collects every 5. > > > All of mine were 10, but once I figured out to edit /etc/cron.d/sysstat they > are now every 1 minute. oh yeah it's every 10 on the 5s. I too need to go to 1minute intervals. > sar has some remarkably opaque documentation, but I'm glad I tracked that > down. It's so incredibly useful. When a machine is acting up often getting it back online is more important than fixing it right then, and most of the system state stuff is lost on reboot / fix. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
