From: Joshua D. Drake <jd@commandprompt.com>
To: Koichi Suzuki <suzuki.koichi@oss.ntt.co.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: josh@agliodbs.com
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-patches@postgresql.org
Subject: Re: [HACKERS] Full page writes improvement, code update
Date: Tue, 10 Apr 2007 18:17:38 -0700
Message-ID: <461C3732.20006@commandprompt.com> (raw)
In-Reply-To: <461C3557.6040201@oss.ntt.co.jp>
References: <460886E8.6040907@oss.ntt.co.jp>
<4609CAC3.7060008@oss.ntt.co.jp>
<1175072848.4386.323.camel@silverbirch.site>
<200703291145.28574.josh@agliodbs.com>
<1175200117.4386.616.camel@silverbirch.site>
<460C611E.6090800@oss.ntt.co.jp>
<27693.1176226131@sss.pgh.pa.us>
<461C3557.6040201@oss.ntt.co.jp>
> In terms of idle time for gzip and other command to archive WAL offline,
> no difference in the environment was given other than the command to
> archive. My guess is because the user time is very large in gzip, it
> has more chance for scheduler to give resource to other processes. In
> the case of cp, idle time is more than 30times longer than user time.
> Pg_compresslog uses seven times longer idle time than user time. On the
> other hand, gzip uses less idle time than user time. Considering the
> total amount of user time, I think it's reasonable measure.
>
> Again, in my proposal, it is not the issue to increase run time
> performance. Issue is to decrease the size of archive log to save the
> storage.
Considering the relatively little amount of storage a transaction log
takes, it would seem to me that the performance angle is more appropriate.
Is it more efficient in other ways besides negligible tps? Possibly more
efficient memory usage? Better restore times for a crashed system?
Sincerely,
Joshua D. Drake
>
> Regards;
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
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-hackers@postgresql.org
Cc: jd@commandprompt.com, suzuki.koichi@oss.ntt.co.jp, tgl@sss.pgh.pa.us, simon@2ndquadrant.com, josh@agliodbs.com, pgsql-patches@postgresql.org
Subject: Re: [HACKERS] Full page writes improvement, code update
In-Reply-To: <461C3732.20006@commandprompt.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