From: | lst_hoe02(at)kwsoft(dot)de |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Maximum insert per second |
Date: | 2011-07-15 08:09:26 |
Message-ID: | 20110715100926.91335pd1uvzhoz8c@webmail.kwsoft.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Zitat von Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>:
> Jenish Vyas <jenishvyas(at)gmail(dot)com> wrote:
>
>> I am able to insert 1190- 1210 records per seconds.
>>
>> Now I just want to know by what extend I could stretch it.
>>
>> What is the maximum insert I can achieve in one second? What is
>> the maximum number of insert postgresql achieved so far?
>
> I don't have hard numbers handy, and I know I don't have the fastest
> hardware out there, but for bulk loads of narrow tables we typically
> see tens of thousands of rows per second. Of course that's with
> "running with scissors" settings. We turn off archiving,
> autovacuum, fsync, full_page_writes, and synchronous_commit; and
> COPY rows within the same transaction which creates the table,
> before creating any indexes. Then we build the indexes, VACUUM
> FREEZE ANALYZE, and change back to a configuration which actually
> preserves the data on a crash.
>
> From memory, I would say on our larger servers we've probably seen
> a max of something on the order of 50,000 rows per second on
> relatively narrow tables, without factoring the index build and
> vacuum times.
>
Are there any numbers around for OLTP like systems? Would be nice to
know what is possible with PostgreSQL in this case.
Regards
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2011-07-15 09:39:46 | Re: Maximum insert per second |
Previous Message | Sergey Konoplev | 2011-07-15 08:04:25 | Re: How to find out hit count or read activities on functions in postgresql 8.4.6 |