Kevin Grittner wrote:
Yeb Havinga <yebhavi...@gmail.com> wrote:
concerning gist indexes:
1) with larger block sizes and hence, larger # entries per gist
page, results in more generic keys of those pages. This in turn
results in a greater number of hits, when the index is queried, so
a larger part of the index is scanned. NB this has nothing to do
with caching / cache sizes; it holds for every IO model. Tests
performed by me showed performance improvements of over 200%.
Since then implementing a speedup has been on my 'want to do
list'.
As I recall, the better performance in your tests was with *smaller*
GiST pages, right? (The above didn't seem entirely clear on that.)
Yes, making pages smaller made index scanning faster.
-- Yeb
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
