From: Madison Kelly <linux@alteeve.com>
To: Tobias Brox <tobias@nordicbet.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Setting "nice" values
Date: Mon, 06 Nov 2006 09:18:03 -0500
Message-ID: <454F441B.1090601@alteeve.com> (raw)
In-Reply-To: <20061106141149.GA7642@oppetid.no>
References: <20061102160057.GA26580@oppetid.no>
<454F3434.4030205@alteeve.com>
<20061106133353.GA22050@oppetid.no>
<454F3D23.6040003@alteeve.com>
<20061106141149.GA7642@oppetid.no>
Tobias Brox wrote:
> [Madison Kelly - Mon at 08:48:19AM -0500]
>> Ah, sorry, long single queries is what you meant.
>
> No - long running single transactions :-) If it's only read-only
> queries, one will probably benefit by having one transaction for every
> query.
>
In this case, what happens is one kinda ugly big transaction is read
into a hash, and then looped through (usually ~10,000 rows). On each
loop another, slightly less ugly query is performed based on the first
query's values now in the hash (these queries being where throttling
might help). Then after the second query is parsed a PDF file is created
(also a big source of slowness). It isn't entirely read-only though
because as the PDFs are created a flag is updated in the given record's
row. So yeah, need to experiment some. :)
Madi
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: linux@alteeve.com, tobias@nordicbet.com, smarlowe@g2switchworks.com
Subject: Re: Setting "nice" values
In-Reply-To: <454F441B.1090601@alteeve.com>
* 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