| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Neil Conway <neilc(at)samurai(dot)com>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: Status of 8.3 patches |
| Date: | 2007-08-20 20:32:33 |
| Message-ID: | 46C9FA61.5060509@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joshua D. Drake wrote:
> Heikki Linnakangas wrote:
>> Bruce Momjian wrote:
>>> o Automatic adjustment of bgwriter_lru_maxpages
>>>
>>> We show this as waiting for performance results. I am thinking we
>>> should hold this for 8.4.
>> Agreed. I spent close to a week trying different benchmarks and
>> configurations and simple test cases on a test server and my laptop, and
>> couldn't demonstrate bgwriter making a positive impact in any
>> configuration I tried. The theory behind the patch is sound, but it
>> looks like a lot more testing and analysis is needed.
>
> Wouldn't real world testing be needed to actually gain insight to this
> patch?
I would expect a fairly static benchmark workload to benefit from having
a bgwriter, more so than more unpredictable real world applications.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-08-20 20:37:04 | Re: Status of 8.3 patches |
| Previous Message | Gregory Stark | 2007-08-20 20:32:18 | Problem with locks |