Is using a ramdisk in situations like this entirely ill-advised then?
When data integrity isn't a huge issue and you really need good write
performance it seems like it wouldn't hurt too much. Unless I am
missing something?
On 20 May 2005, at 02:45, Christopher Kings-Lynne wrote:
I'm
I am interested in optimising write performance as well, the machine
I am testing on is maxing out around 450 UPDATEs a second which is
quite quick I suppose. I haven't tried turning fsync off yet. The
table has...a lot of indices as well. They are mostly pretty simple
partial indexes
On Thu, May 19, 2005 at 05:21:07PM -0500, Steve Bergman wrote:
I'm doing the writes individually. Is there a better way? Combining
them all into a transaction or something?
Batching them all in one or a few transactions will speed it up a _lot_.
Using COPY would help a bit more on top of
Steinar H. Gunderson [EMAIL PROTECTED] writes:
On Thu, May 19, 2005 at 05:21:07PM -0500, Steve Bergman wrote:
I'm doing the writes individually. Is there a better way? Combining
them all into a transaction or something?
Batching them all in one or a few transactions will speed it up a
I'm doing the writes individually. Is there a better way? Combining
them all into a transaction or something?
Use COPY of course :)
Or at worst bundle 1000 inserts at a time in a transation...
And if you seriously do not care about your data at all, set fsync = off
in you postgresql.conf for
