Re: [ADMIN] Details about pg_stat_bgwriter

2010-06-09 Thread Scott Marlowe
On Tue, Jun 8, 2010 at 11:14 PM, Greg Smith g...@2ndquadrant.com wrote: Greg Smith wrote: You don't much with a single snapshot of pg_stat_bgwriter data.  Try saving this instead: select *,now() from pg_stat_bgwriter; And then take another snapshot at least a few hours later, preferably the

Re: [ADMIN] Details about pg_stat_bgwriter

2010-06-09 Thread Greg Smith
Scott Marlowe wrote: -Average checkpoint frequency -Average size of each checkpoint -Average rate at which new buffers are allocated -Average rate of writes out of the buffer cache -Percentage of writes done by checkpoints, the background writer LRU cleaner, and client backends I think

Re: [ADMIN] Details about pg_stat_bgwriter

2010-06-09 Thread Thomas Kellerer
Greg Smith, 09.06.2010 07:14: I probably should have explained the next part. I've now shared what I do with this information at http://www.pgcon.org/2010/schedule/events/218.en.html Basically, if you put the data from the two snapshots into one of the Statistics Spreadsheet versions, you'll

Re: [ADMIN] Details about pg_stat_bgwriter

2010-06-09 Thread Greg Smith
Thomas Kellerer wrote: I don't think we have a caching issue though, it's just one (regular) bulk import that does some heavy writes which we need to tune. Read performance is absolutely fine, but everything around vacuum and checkpointing seems to slow down the import massively. So would

[ADMIN] Details about pg_stat_bgwriter

2010-06-08 Thread Thomas Kellerer
Hi, I'm trying to understand the information shown in pg_stat_bgwriter. If I want to identify a possible bottleneck with the bgwriter, for what kind of numbers do I need to watch out? Are the following values OK, or do they indicate that I need to tune my configuration? checkpoints_timed :

Re: [ADMIN] Details about pg_stat_bgwriter

2010-06-08 Thread Greg Smith
Thomas Kellerer wrote: If I want to identify a possible bottleneck with the bgwriter, for what kind of numbers do I need to watch out? You don't much with a single snapshot of pg_stat_bgwriter data. Try saving this instead: select *,now() from pg_stat_bgwriter; And then take another

Re: [ADMIN] Details about pg_stat_bgwriter

2010-06-08 Thread Thomas Kellerer
Greg Smith wrote on 08.06.2010 19:30: Thomas Kellerer wrote: If I want to identify a possible bottleneck with the bgwriter, for what kind of numbers do I need to watch out? You don't much with a single snapshot of pg_stat_bgwriter data. Try saving this instead: select *,now() from

Re: [ADMIN] Details about pg_stat_bgwriter

2010-06-08 Thread Greg Smith
Greg Smith wrote: You don't much with a single snapshot of pg_stat_bgwriter data. Try saving this instead: select *,now() from pg_stat_bgwriter; And then take another snapshot at least a few hours later, preferably the next day. With two snapshots and timestamps on them, then it's possible