From: | Michael Nolan <htfoot(at)gmail(dot)com> |
---|---|
To: | Florian Weimer <fweimer(at)bfk(dot)de> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: SSDs with Postgresql? |
Date: | 2011-04-26 16:26:01 |
Message-ID: | BANLkTikm9G-3XKe5cM9z=PsK9kCPUtt7aA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Apr 21, 2011 at 10:33 AM, Florian Weimer <fweimer(at)bfk(dot)de> wrote:
> * Greg Smith:
>
> > The fact that every row update can temporarily use more than 8K means
> > that actual write throughput on the WAL can be shockingly large. The
> > smallest customer I work with regularly has a 50GB database, yet they
> > write 20GB of WAL every day. You can imagine how much WAL is
> > generated daily on systems with terabyte databases.
>
> Interesting. Is there an easy way to monitor WAL traffic in away? It
> does not have to be finegrained, but it might be helpful to know if
> we're doing 10 GB, 100 GB or 1 TB of WAL traffic on a particular
> database, should the question of SSDs ever come up.
>
> If you archive your WAL files, wouldn't that give you a pretty good
indication of write activity?
For example, yesterday I archived 74 WAL files, each 16MB. That's about 1.2
gigabytes for a database that takes up about 58 GB.
--
Mike Nolan
From | Date | Subject | |
---|---|---|---|
Next Message | Vick Khera | 2011-04-26 16:38:31 | Re: [GENERAL]auto vacuum during restore |
Previous Message | Carlos Sotto Maior (SIM) | 2011-04-26 16:24:53 | "pg_control version number" after 9.0.4 installation |