On Mon, May 16, 2011 at 12:49 AM, Jesper Krogh <jesper@xxxxxxxx> wrote: >> To me it seems like a robust and fairly trivial way to to get better >> numbers. The >> fear is that the OS-cache is too much in flux to get any stable numbers >> out >> of it. > > Ok, it may not work as well with index'es, since having 1% in cache may very > well mean that 90% of all requested blocks are there.. for tables in should > be more trivial. Tables can have hot spots, too. Consider a table that holds calendar reservations. Reservations can be inserted, updated, deleted. But typically, the most recent data will be what is most actively modified, and the older data will be relatively more (though not completely) static, and less frequently accessed. Such examples are common in many real-world applications. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
