| From: | Decibel! <decibel(at)decibel(dot)org> |
|---|---|
| To: | Florian Weimer <fweimer(at)bfk(dot)de> |
| Cc: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Read-ahead and parallelism in redo recovery |
| Date: | 2008-02-29 19:59:30 |
| Message-ID: | 3AAB6457-A03A-4DAA-8457-743F712F7289@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 29, 2008, at 8:10 AM, Florian Weimer wrote:
> In the end, I wouldn't be surprised if for most loads, cache warming
> effects dominated recovery times, at least when the machine is not
> starved on RAM.
Uh... that's exactly what all the synchronous reads are doing...
warming the cache. And synchronous reads are only fast if the system
understands what's going on and reads a good chunk of data in at
once. I don't know that that happens.
Perhaps a good short-term measure would be to have recovery allocate
a 16M buffer and read in entire xlog files at once.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-02-29 20:43:51 | Re: Read-ahead and parallelism in redo recovery |
| Previous Message | Tom Lane | 2008-02-29 19:47:51 | Re: bug or not bug, xmlvalidate(xml, text) can read and show one line from file |