From: Chris Mair <list@1006.org>
To: pgsql-performance@postgresql.org
Subject: Re: SOLVED: insertion of bytea
Date: Mon, 31 Oct 2005 15:29:17 +0100
Message-ID: <1130768957.6383.37.camel@dell.1006.org> (raw)
In-Reply-To: <34757.193.206.186.101.1130420404.squirrel@www.endian.it>
References: <54222.193.206.186.101.1130247876.squirrel@www.endian.it>
<20051025140549.GC17398@mathom.us>
<34757.193.206.186.101.1130420404.squirrel@www.endian.it>
> I'm CPU-bound with an I/O well below what my disks could do :(
> [...]
>
> PS1: someone off-list suggested using oprofile, which I will do.
I've used oprofile and found out that with my test client (lots of
bytea inserts) the server burns a lot of CPU time in pglz_compress.
I'm using random data and my production data will be closed to random
(due to noise!), so compression is of course pointless.
By using
alter table dbtest alter img set storage external;
I can tell the server not to compress.
On a test box this brought net insert rate up by 50%,
which is enough to meet the requirements.
Thanks again :)
Bye, Chris.
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: list@1006.org
Subject: Re: SOLVED: insertion of bytea
In-Reply-To: <1130768957.6383.37.camel@dell.1006.org>
* 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