From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Performance lossage in checkpoint dumping |
Date: | 2001-02-17 02:47:25 |
Message-ID: | 200102170247.VAA24435@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 3. Blind write is gratuitously inefficient: it does separate open,
> seek, write, close kernel calls for every request. This was the right
> thing in 7.0.*, because backends relatively seldom did blind writes and
> even less often needed to blindwrite multiple pages of a single relation
> in succession. But the typical usage has changed a lot.
>
>
> I am thinking it'd be a good idea if blind write went through fd.c and
> thus was able to re-use open file descriptors, just like normal writes.
> This should improve the efficiency of dumping dirty buffers during
> checkpoint by a noticeable amount.
I totally agree the current code is broken. I am reading what you say
and am thinking, "Oh well, we lose there, but at least we only open a
relation once and do them in one shot." Now I am hearing that is not
true, and it is a performance problem.
This is not a total surprise. We have that stuff pretty well
streamlined for the old behavour. Now that things have changed, I can
see the need to reevaluate stuff.
Not sure how to handle the beta issue though.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-17 03:06:28 | Re: Performance lossage in checkpoint dumping |
Previous Message | Tom Lane | 2001-02-17 02:31:48 | Performance lossage in checkpoint dumping |