Re: [PERFORM] [HACKERS] fsync vs open_sync

2004-08-13 Thread pgsql
Guys, just so you know: OSDL did some testing and found Ext3 to be perhaps the worst FS for PostgreSQL -- although this testing was with the default options. Ext3 involved an almost 40% write performance penalty compared with Ext2, whereas the penalty for ReiserFS and JFS was less than

Re: [PERFORM] [HACKERS] fsync vs open_sync

2004-08-11 Thread Steve Bergman
On Tue, 2004-08-10 at 10:18 -0700, Josh Berkus wrote: Guys, just so you know: OSDL did some testing and found Ext3 to be perhaps the worst FS for PostgreSQL -- although this testing was with the default options. Ext3 involved an almost 40% write performance penalty compared with Ext2,

Re: [PERFORM] [HACKERS] fsync vs open_sync

2004-08-11 Thread Gaetano Mendola
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: |Anyway, with fsync enabled using standard fsync(), I get roughly | |300-400 | |inserts per second. With fsync disabled, I get about 7000 inserts per |second. When I re-enable fsync but use the open_sync option, I can get

Re: [PERFORM] [HACKERS] fsync vs open_sync

2004-08-10 Thread pgsql
Anyway, with fsync enabled using standard fsync(), I get roughly 300-400 inserts per second. With fsync disabled, I get about 7000 inserts per second. When I re-enable fsync but use the open_sync option, I can get about 2500 inserts per second. You are getting 300-400 inserts/sec with fsync

Re: [PERFORM] [HACKERS] fsync vs open_sync

2004-08-10 Thread Josh Berkus
Guys, just so you know: OSDL did some testing and found Ext3 to be perhaps the worst FS for PostgreSQL -- although this testing was with the default options. Ext3 involved an almost 40% write performance penalty compared with Ext2, whereas the penalty for ReiserFS and JFS was less than 10%.