| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | shridhar_daithankar(at)persistent(dot)co(dot)in |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Insert performance |
| Date: | 2003-08-18 15:52:43 |
| Message-ID: | 1061221963.2620.4.camel@fuji.krosing.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Shridhar Daithankar kirjutas E, 18.08.2003 kell 09:21:
> On 16 Aug 2003 at 11:40, Josh Berkus wrote:
>
> > Shridhar,
> >
> > > Unfortunately he can not use copy due to some constraints.
> >
> > Why not use COPY to load the table, and then apply the constraints by query
> > afterwords? It might not be faster, but then again it might.
>
> Lol.. The constraints I mentioned weren't database constraints..
Can't you still apply them later ;)
My own experimentation also got numbers in 9k/sec range (on a quad
1.3GHz Xeons, 2GM mem, 50MB/sec raid) when doing 10-20 parallel runs of
~1000 inserts/transaction.
Performance dropped to ~300/sec (at about 60M rows) when I added an
index (primary key) - as I did random inserts, the hit rates for index
pages were probably low.
--------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2003-08-18 16:02:27 | Re: Insert performance |
| Previous Message | pginfo | 2003-08-18 14:58:49 | bad join performance |