| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Aren Cambre <aren(at)arencambre(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgres refusing to use >1 core |
| Date: | 2011-05-23 05:22:51 |
| Message-ID: | 4DD9EF2B.9030104@postnewspapers.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 23/05/11 12:09, Aren Cambre wrote:
> Also, thanks for the advice on batching my queries. I am now using a
> very efficient bulk data read and write methods for Postgres.
>
> My program bulk reads 100,000 rows, processes those rows (during which
> it does a few SELECTs), and then writes 100,000 rows at a time.
>
> It cycles through this until it has processed all 12,000,000 rows.
>
> This, plus the parallelism fix, will probably convert this 30 hour
> program to a <2 hour program.
It's always good to hear when these things work out. Thanks for
reporting back.
Using the set-based nature of relational databases to your advantage,
writing smarter queries that do more work server-side with fewer
round-trips, and effective batching can make a huge difference.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre C | 2011-05-23 10:53:57 | Re: FW: KVP table vs. hstore - hstore performance (Was: Postgres NoSQL emulation) |
| Previous Message | Aren Cambre | 2011-05-23 04:09:49 | Re: Postgres refusing to use >1 core |