Re: insert/update tps slow with indices on table > 1M rows - Mailing list pgsql-performance

From Tom Lane
Subject Re: insert/update tps slow with indices on table > 1M rows
Date
Msg-id 6656.1212619939@sss.pgh.pa.us
Whole thread Raw
In response to Re: insert/update tps slow with indices on table > 1M rows  (andrew klassen <aptklassen@yahoo.com>)
List pgsql-performance
andrew klassen <aptklassen@yahoo.com> writes:
> I am using the c-library interface and for these particular transactions
> I preload PREPARE statements. Then as I get requests, I issue a BEGIN,
> followed by at most 300 EXECUTES and then a COMMIT. That is the
> general scenario. What value beyond 300 should I try?

Well, you could try numbers in the low thousands, but you'll probably
get only incremental improvement.

> Also, how might COPY (which involves file I/O) improve the
> above scenario?

COPY needn't involve file I/O.  If you are using libpq you can push
anything you want into PQputCopyData.  This would involve formatting
the data according to COPY's escaping rules, which are rather different
from straight SQL, but I doubt it'd be a huge amount of code.  Seems
worth trying.

            regards, tom lane

pgsql-performance by date:

Previous
From: PFC
Date:
Subject: Re: insert/update tps slow with indices on table > 1M rows
Next
From: Greg Smith
Date:
Subject: Re: RAM / Disk ratio, any rule?