Re: Replaying 48 WAL files takes 80 minutes
От | Jeff Trout |
---|---|
Тема | Re: Replaying 48 WAL files takes 80 minutes |
Дата | |
Msg-id | B9F96C1F-D0D7-4151-8D15-04CCA93AC369@torgo.978.org обсуждение исходный текст |
Ответ на | Re: Replaying 48 WAL files takes 80 minutes (Jeff Janes <jeff.janes@gmail.com>) |
Список | pgsql-performance |
On Oct 29, 2012, at 12:42 PM, Jeff Janes wrote: > On Mon, Oct 29, 2012 at 6:05 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote: >> I am configuring streaming replication with hot standby >> with PostgreSQL 9.1.3 on RHEL 6 (kernel 2.6.32-220.el6.x86_64). >> PostgreSQL was compiled from source. >> >> It works fine, except that starting the standby took for ever: >> it took the system more than 80 minutes to replay 48 WAL files >> and connect to the primary. >> >> Can anybody think of an explanation why it takes that long? > > Could the slow log files be replaying into randomly scattered pages > which are not yet in RAM? > > Do you have sar or vmstat reports? > If you do not have good random io performance log replay is nearly unbearable. (I've run into this before many times) Also, what io scheduler are you using? if it is cfq change that to deadline or noop. that can make a huge difference. -- Jeff Trout <jeff@jefftrout.com
В списке pgsql-performance по дате отправления: