On Thu, 2004-12-16 at 11:07, Neil Conway wrote:
> Zeugswetter Andreas DAZ SD wrote:
> > This has the disadvantage of converging against 0 dirty pages.
> > A system that has less than maxpages dirty will write every page with
> > every bgwriter run.
>
> Yeah, I'm concerned about the bgwriter being overly aggressive if we
> disable bgwriter_percent. If we leave the settings as they are (delay =
> 200, maxpages = 100, shared_buffers = 1000 by default), we will be
> writing all the dirty pages to disk every 2 seconds, which seems far too
> much.
>
> It might also be good to reduce the delay, in order to more proactively
> keep the LRUs clean (e.g. scanning to find N dirty pages once per second
> is likely to reach father away from the LRU than scanning for N/M pages
> once per 1/M seconds). On the other hand the more often the bgwriter
> scans the buffer pool, the more times the BufMgrLock needs to be
> acquired -- and in a system in which pages aren't being dirtied very
> rapidly (or the dirtied pages tend to be very hot), each of those scans
> is going to take a while to find enough dirty pages using #2. So perhaps
> it is best to leave the delay as is for 8.0.
I think this is probably the right thing to do, since the majority of
users will have low/medium workloads, not the extremes of performance
that we have mainly been discussing.
> > This might have the disadvantage of either leaving too much for the
> > checkpoint or writing too many dirty pages in one run. Is writing a lot
> > in one run actually a problem though ? Or does the bgwriter pause
> > periodically while writing the pages of one run ?
>
> The bgwriter does not pause between writing pages. What would be the
> point of doing that? The kernel is going to be caching the write() anyway.
>
> > If this is expressed in pages it would naturally need to be more than the
> > current maxpages (to accomodate for clean pages). The suggested 2% sounded
> > way too low for me (that leaves 98% to the checkpoint).
>
> I agree this might be a problem, but it doesn't necessarily leave 98% to
> be written at checkpoint: if the buffers in the LRU change over time,
> the set of pages searched by the bgwriter will also change.
Agreed.
> I'm not sure
> how quickly the pages near the LRU change in a "typical workload";
> moreover, I think this would vary between different workloads.
Yes, clearly we need to be able to change the parameters according to
the workload....and long term have them vary as needs change.
My concern at the moment is that the bgwriter_delay looks to me like it
needs to be set lower for busier workloads, yet that is not possible
because of the contention for the BufMgrLock. Investigating optimal
parameter settings isn't possible while this contention exists.
Incidentally, setting debug_shared_buffers also causes some contention
which I'll look at reducing for 8.1, so it can be be used more
frequently as a log_ setting.
--
Best Regards, Simon Riggs
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
