This is the another bonnie++ test result with version 1.03
Delete files in random order...done.
Version 1.03e ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
myserver 300M 13150 7 12713 1 13067 4 72426 53 +++++ +++ +++++ +++
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 1048 2 +++++ +++ 2322 3 985 2 +++++ +++ 1797 3
myserver,300M,13150,7,12713,1,13067,4,72426,53,+++++,+++,+++++,+++,16,1048,2,+++++,+++,2322,3,985,2,+++++,+++,1797,3
Also I attached bon_csv2html output for both version of bonnie++
Thanks in advance.
On Thu, Jan 22, 2009 at 7:14 PM, Merlin Moncure <mmoncure@gmail.com> wrote:
> On 1/22/09, Ibrahim Harrani <ibrahim.harrani@gmail.com> wrote:
>>
>> Is this rate is normal or not? What can I do to improve tps and insert
>> performance?
>>
>> postgresql.conf
>>
>> shared_buffers = 800MB # min 128kB or max_connections*16kB
>> work_mem = 2MB # min 64kB
>> maintenance_work_mem = 32MB # min 1MB
>
> I would raise maintenance_work_mem, although it's unrelated to your issue.
>
>> max_connections = 600 # (change requires restart)
>> max_fsm_relations = 2000 # min 100, ~70 bytes each
>> synchronous_commit = off
>
> Something is very wrong. 40tps is low, even for sata raid 1, but
> absolutely terrible with synchronous_commit = off. This suggests you
> are problems are read related and not sync related. Can you rerun
> pgbench using the custom sql feature, passing insert statements?
>
> Are you sure nothing else is going on/wrong with the box? Can we see a
> bonnie++ run?
>
> merlin
>