Amit Kapila <amit.kapil...@gmail.com> wrote: > Overall I agree that following Robert's idea will increase the > time to make database server up and reach a state where apps can > connect and start operations,
I agree that warming the cache before beginning to apply WAL would be best. > but I think atleast with such an approach we can claim that after > warming buffers with pg_hibernator apps will always have > performance greater than equal to the case when there is no > pg_hibernator. I would be careful of this claim in a NUMA environment. The whole reason I investigated NUMA issues and wrote the NUMA patch is that a customer had terrible performance which turned out to be caused by cache warming using a single connection (and thus a single process, and thus a single NUMA memory node). To ensure that this doesn't trash performance on machines with many cores and memory nodes, it would be best to try to spread the data around among nodes. One simple way of doing this would be to find some way to use multiple processes in hopes that they would run on difference CPU packages. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
