| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: High CPU usage / load average after upgrading to Ubuntu 12.04 |
| Date: | 2013-02-26 21:30:42 |
| Message-ID: | CAMkU=1zPMB_G1tZPW8cYnYbh2aQ81o5LPuaXg=C63Odyy1yZCw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Feb 15, 2013 at 10:52 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> On Fri, Feb 15, 2013 at 11:26 AM, Josh Berkus <josh(at)agliodbs(dot)com> 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.
sar has some remarkably opaque documentation, but I'm glad I tracked that
down.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Costin Oproiu | 2013-02-26 21:45:57 | pgbench intriguing results: better tps figures for larger scale factor |
| Previous Message | Matt Daw | 2013-02-26 19:35:45 | Estimation question... |