Re: Compression of full-page-writes - Mailing list pgsql-hackers

From Haribabu kommi
Subject Re: Compression of full-page-writes
Date
Msg-id 8977CB36860C5843884E0A18D8747B0372BC790D@szxeml558-mbs.china.huawei.com
Whole thread Raw
In response to Re: Compression of full-page-writes  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
Responses Re: Compression of full-page-writes  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
List pgsql-hackers
On 08 October 2013 15:22 KONDO Mitsumasa wrote:
> (2013/10/08 17:33), Haribabu kommi wrote:
>> The checkpoint_timeout and checkpoint_segments are increased to make sure no checkpoint happens during the test
run.

>Your setting is easy occurred checkpoint in checkpoint_segments = 256. I don't know number of disks in your test
server,in my test server which has 4 magnetic disk(1.5k rpm), postgres generates 50 - 100 WALs per minutes.
 

A manual checkpoint is executed before starting of the test and verified as no checkpoint happened during the run by
increasingthe "checkpoint_warning".
 

>And I cannot understand your setting which is sync_commit = off. This setting tend to cause cpu bottle-neck and
data-loss.It is not general in database usage.
 
Therefore, your test is not fair comparison for Fujii's patch.

I chosen the sync_commit=off mode because it generates more tps, thus it increases the volume of WAL.
I will test with sync_commit=on mode and provide the test results.

Regards,
Hari babu.

pgsql-hackers by date:

Previous
From: shailesh singh
Date:
Subject: Urgent Help Required
Next
From: Rushabh Lathia
Date:
Subject: Re: insert throw error when year field len > 4 for timestamptz datatype