DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	b=x0xeUy6ccv2WcKL4ukxihFZ/046VQbwcOmWhfy3pDmoc5y7LVj/ShyoE/HVcK8sgdA
	4iS7/a0S80Hquvfrl6rNqH5MGca0CX37877PI2E1psEWv/ldniiCIt3vtAc02nUwLR1B
	Pq/2wrGAUrcPqWsBQceVC1l/omxF1qkK+xuis=
MIME-Version: 1.0
In-Reply-To: <4BFFA32D.8010009@iathh.de>
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>
From: Rob Wultsch <wultsch@gmail.com>
Date: Fri, 28 May 2010 10:07:42 -0700
Message-ID: <AANLkTinmMF0ZXWYmfIuIx4BESK7-RvvjOSDu0dchkeM7@mail.gmail.com>
Subject: Re: performance of temporary vs. regular tables
To: Joachim Worringen <joachim.worringen@iathh.de>
Cc: pgsql-performance@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, May 28, 2010 at 4:04 AM, Joachim Worringen
<joachim.worringen@iathh.de> wrote:
> On 05/26/2010 06:03 PM, Joachim Worringen wrote:
>>
>> Am 25.05.2010 12:41, schrieb Andres Freund:
>>>
>>> On Tuesday 25 May 2010 11:00:24 Joachim Worringen wrote:
>>>>
>>>> Thanks. So, the Write-Ahead-Logging (being used or not) does not matte=
r?
>>>
>>> It does matter quite significantly in my experience. Both from an io
>>> and a cpu
>>> overhead perspective.
>>
>> O.k., looks as if I have to make my own experience... I'll let you know
>> if possible.
>
> As promised, I did a tiny benchmark - basically, 8 empty tables are fille=
d
> with 100k rows each within 8 transactions (somewhat typically for my
> application). The test machine has 4 cores, 64G RAM and RAID1 10k drives =
for
> data.
>
> # INSERTs into a TEMPORARY table:
> [joachim@testsrv scaling]$ time pb query -d scaling_qry_1.xml
>
> real =A0 =A03m18.242s
> user =A0 =A01m59.074s
> sys =A0 =A0 1m51.001s
>
> # INSERTs into a standard table:
> [joachim@testsrv scaling]$ time pb query -d scaling_qry_1.xml
>
> real =A0 =A03m35.090s
> user =A0 =A02m5.295s
> sys =A0 =A0 2m2.307s
>
> Thus, there is a slight hit of about 10% (which may even be within
> meausrement variations) - your milage will vary.
>
> =A0Joachim
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org=
)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
I think it would be interesting to create a ram disk and insert into
it. In the MySQL community even thought MyISAM has fallen out of use
the Memory table (based on MyISAM) is still somewhat used.


--=20
Rob Wultsch
wultsch@gmail.com