From: Joachim Worringen <joachim.worringen@iathh.de>
To: Pierre C <lists@peufeu.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: performance of temporary vs. regular tables
Date: Wed, 02 Jun 2010 14:54:22 +0200
Message-ID: <4C06547E.2010104@iathh.de> (raw)
In-Reply-To: <op.vdn3kgtheorkce@immo.peufeu.com>
References: <4BFB837C.6010005@iathh.de>
<AANLkTik4_exB6U3GlfLMNIgPSk0G3RVQ8fWBTzwekrke@mail.gmail.com>
<4BFB91A8.20805@iathh.de>
<201005251241.59605.andres@anarazel.de>
<4BFD4643.9010901@iathh.de>
<4BFFA32D.8010009@iathh.de>
<op.vdn3kgtheorkce@immo.peufeu.com>
Am 02.06.2010 12:03, schrieb Pierre C:
> Usually WAL causes a much larger performance hit than this.
>
> Since the following command :
>
> CREATE TABLE tmp AS SELECT n FROM generate_series(1,1000000) AS n
>
> which inserts 1M rows takes 1.6 seconds on my desktop, your 800k rows
> INSERT taking more than 3 minutes is a bit suspicious unless :
>
> - you got huge fields that need TOASTing ; in this case TOAST
> compression will eat a lot of CPU and you're benchmarking TOAST, not the
> rest of the system
> - you got some non-indexed foreign key
> - some other reason ?
Yes, the "other" reason is that I am not issueing a single SQL command,
but import data from plain ASCII files through the Pyhton-based
framework into the database.
The difference between your measurement and my measurent is the upper
potential of improvement for my system (which has, on the other hand,
the advantage of being a bit more powerful and flexible than a single
SQL statement....;-) )
Joachim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: joachim.worringen@iathh.de, lists@peufeu.com
Subject: Re: performance of temporary vs. regular tables
In-Reply-To: <4C06547E.2010104@iathh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox