"Jignesh K. Shah" <J.K.Shah@xxxxxxx> writes: > Can we do a vote on which specific performance features we want to test? > > Many of the improvements may not be visible through this standard tests so > feedback on testing methology for those is also appreciated. > * Visibility map - Reduce Vacuum overhead - (I think I can time vacuum with > some usage on both databases) Timing vacuum is kind of pointless -- the only thing that matters is whether it's "fast enough". But it is worth saying that good benchmarks should include normal vacuum runs. Benchmarks which don't run long enough to trigger vacuum aren't realistic. > * Prefetch IO with posix_fadvice () - Though I am not sure if it is supported > on UNIX or not (but can be tested by standard tests) Well clearly this is my favourite :) AFAIK Opensolaris doesn't implement posix_fadvise() so there's no benefit. It would be great to hear if you could catch the ear of the right people to get an implementation committed. Depending on how the i/o scheduler system is written it might not even be hard -- the Linux implementation of WILLNEED is all of 20 lines. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
