Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Read-ahead and parallelism in redo recovery
- 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: Fri, 29 Feb 2008 13:59:30 -0600
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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- Follow-Ups:
- Re: Read-ahead and parallelism in redo recovery
- From: Tom Lane
- Re: Read-ahead and parallelism in redo recovery
- From: Heikki Linnakangas
- Re: Read-ahead and parallelism in redo recovery
- References:
- Read-ahead and parallelism in redo recovery
- From: Pavan Deolasee
- Re: Read-ahead and parallelism in redo recovery
- From: Florian Weimer
- Read-ahead and parallelism in redo recovery
- Prev by Date: Re: [BUGS] bug or not bug, xmlvalidate(xml, text) can read and show one line from file
- Next by Date: Re: Read-ahead and parallelism in redo recovery
- Previous by thread: Re: Read-ahead and parallelism in redo recovery
- Next by thread: Re: Read-ahead and parallelism in redo recovery
- Indexes: