pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedEstimating WAL volume
2+ messages / 2 participants
[nested] [flat]
* Estimating WAL volume
@ 2007-07-12 03:10 Greg Smith <gsmith@gregsmith.com>
0 siblings, 1 reply; 2+ messages in thread
From: Greg Smith @ 2007-07-12 03:10 UTC (permalink / raw)
To: pgsql-performance
All this talk of WAL writing lately has me wondering something I haven't
spent enough time looking at the source to figure out myself this
week...any good rules of thumb out there for estimating WAL volume? I'm
used to just measuring it via benchmarking but it strikes me a formula
would be nice to have for pre-planning.
For example, if I have a table where a typical row is X bytes wide, and
I'm updating Y of those per second, what's the expected write rate of WAL
volume? Some % of those writes are going to be full pages; what's
typical? How much does the number and complexity of indexes factor into
things--just add the width of the index in bytes to the size of the
record, or is it worse than that?
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Estimating WAL volume
@ 2007-07-16 08:02 Simon Riggs <simon@2ndquadrant.com>
parent: Greg Smith <gsmith@gregsmith.com>
0 siblings, 0 replies; 2+ messages in thread
From: Simon Riggs @ 2007-07-16 08:02 UTC (permalink / raw)
To: Greg Smith <gsmith@gregsmith.com>; +Cc: pgsql-performance
On Wed, 2007-07-11 at 23:10 -0400, Greg Smith wrote:
> All this talk of WAL writing lately has me wondering something I haven't
> spent enough time looking at the source to figure out myself this
> week...any good rules of thumb out there for estimating WAL volume? I'm
> used to just measuring it via benchmarking but it strikes me a formula
> would be nice to have for pre-planning.
>
> For example, if I have a table where a typical row is X bytes wide, and
> I'm updating Y of those per second, what's the expected write rate of WAL
> volume? Some % of those writes are going to be full pages; what's
> typical? How much does the number and complexity of indexes factor into
> things--just add the width of the index in bytes to the size of the
> record, or is it worse than that?
I published an analysis of WAL traffic from Greg Stark earlier, based
upon xlogdump.
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php
Other details of WAL volumes are in the code. Further analysis would be
welcome, to assist discussions of where to optimize next.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2007-07-16 08:02 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-07-12 03:10 Estimating WAL volume Greg Smith <gsmith@gregsmith.com>
2007-07-16 08:02 ` Simon Riggs <simon@2ndquadrant.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox