From: | "Mark Harris" <mharris(at)esri(dot)com> |
---|---|
To: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | reading large BYTEA type is slower than expected |
Date: | 2007-05-18 17:11:51 |
Message-ID: | D7BFFE348C53EF4E8AA0698B1E395FA9085ABD49@flybywire.esri.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
We have recently ported our application to the postgres database. For
the most part performance has not been an issue; however there is one
situation that is a problem and that is the initial read of rows
containing BYTEA values that have an average size of 2 kilobytes or
greater. For BYTEA values postgres requires as much 3 seconds to read
the values from disk into its buffer cache. After the initial read into
buffer cache, performance is comparable to other commercial DBMS that we
have ported to. As would be expected the commercial DBMS are also slower
to display data that is not already in the buffer cache, but the
magnitude of difference for postgres for this type of data read from
disk as opposed to read from buffer cache is much greater.
We have vacuumed the table and played around with the database
initialization parameters in the postgresql.conf. Neither helped with
this problem.
Does anyone have any tips on improving the read from disk performance of
BYTEA data that is typically 2KB or larger?
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | cyber-postgres | 2007-05-18 17:43:40 | 121+ million record table perf problems |
Previous Message | Liviu Ionescu | 2007-05-18 16:49:30 | Re: performance drop on 8.2.4, reverting to 8.1.4 |