Message-ID: <51CACD6F.2060804@vmware.com>
Date: Wed, 26 Jun 2013 14:15:59 +0300
From: Heikki Linnakangas <hlinnakangas@vmware.com>
Organization: VMware
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>
CC: Robert Haas <robertmhaas@gmail.com>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Improvement of checkpoint IO scheduler for stable transaction
 responses
References: <51B5AFB1.5030404@lab.ntt.co.jp> <51BDCB6C.1090507@vmware.com>
 <51BEB6F5.7070907@lab.ntt.co.jp> <51C40EF4.1080201@lab.ntt.co.jp>
 <51C9D03B.10107@vmware.com>
 <CA+TgmoZ+ofyg4e+hRBTnnfrC7M2ATX-Pg0k4AtyHx60A+_DFhQ@mail.gmail.com>
 <51C9FD5C.5050706@vmware.com> <51CAA84C.7030901@lab.ntt.co.jp>
In-Reply-To: <51CAA84C.7030901@lab.ntt.co.jp>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 26.06.2013 11:37, KONDO Mitsumasa wrote:
>>> On Tue, Jun 25, 2013 at 1:15 PM, Heikki Linnakangas
>>>> Hmm, so the write patch doesn't do much, but the fsync patch makes
>>>> the response
>>>> times somewhat smoother. I'd suggest that we drop the write patch
>>>> for now, and focus on the fsyncs.
>
> Write patch is effective in TPS!

Your test results don't agree with that. You got 3465.96 TPS with the 
write patch, and 3474.62 and 3469.03 without it. The fsync+write 
combination got slightly more TPS than just the fsync patch, but only by 
about 1%, and then the response times were worse.

- Heikki


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers