pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: [HACKERS] fsync vs open_sync
20+ messages / 10 participants
[nested] [flat]
* Re: [HACKERS] fsync vs open_sync
@ 2004-08-10 15:25 Merlin Moncure <merlin.moncure@rcsonline.com>
0 siblings, 2 replies; 20+ messages in thread
From: Merlin Moncure @ 2004-08-10 15:25 UTC (permalink / raw)
To: pgsql@mohawksoft.com; +Cc: pgsql-performance
> 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 on? If you don't mind me
asking, what's your hardware? (also, have you checked fsync on #s with
the new bgwriter in 7.5?)
Merlin
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: [HACKERS] fsync vs open_sync
@ 2004-08-10 15:54 pgsql@mohawksoft.com
parent: Merlin Moncure <merlin.moncure@rcsonline.com>
1 sibling, 1 reply; 20+ messages in thread
From: pgsql@mohawksoft.com @ 2004-08-10 15:54 UTC (permalink / raw)
To: Merlin Moncure <merlin.moncure@rcsonline.com>; +Cc: pgsql-performance
>> 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 on? If you don't mind me
> asking, what's your hardware? (also, have you checked fsync on #s with
> the new bgwriter in 7.5?)
>
300 inserts persecond with fsync on using fdatasync. 2500 inserts per
second with fsync on using open_sync.
[mwoodward@penguin-021 mwoodward]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.40GHz
stepping : 5
cpu MHz : 2399.373
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips : 4784.12
Linux node1 2.4.25 #1 Mon Mar 22 13:33:41 EST 2004 i686 i686 i386 GNU/Linux
ide2: BM-DMA at 0xc400-0xc407, BIOS settings: hde:pio, hdf:pio
hde: Maxtor 6Y200P0, ATA DISK drive
hde: attached ide-disk driver.
hde: host protected area => 1
hde: 398297088 sectors (203928 MB) w/7936KiB Cache, CHS=24792/255/63,
UDMA(100)
PDC20268: IDE controller at PCI slot 06:05.0
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: [HACKERS] fsync vs open_sync
@ 2004-08-10 17:18 Josh Berkus <josh@agliodbs.com>
parent: Merlin Moncure <merlin.moncure@rcsonline.com>
1 sibling, 2 replies; 20+ messages in thread
From: Josh Berkus @ 2004-08-10 17:18 UTC (permalink / raw)
To: Merlin Moncure <merlin.moncure@rcsonline.com>; pgsql@mohawksoft.com; +Cc: pgsql-performance
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%.
This concurs with my personal experience.
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: [HACKERS] fsync vs open_sync
@ 2004-08-10 18:04 pgsql@mohawksoft.com
parent: Josh Berkus <josh@agliodbs.com>
1 sibling, 0 replies; 20+ messages in thread
From: pgsql@mohawksoft.com @ 2004-08-10 18:04 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: Merlin Moncure <merlin.moncure@rcsonline.com>; pgsql-performance
> 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%.
>
> This concurs with my personal experience.
I had exactly the same experience
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-08-11 16:37 Merlin Moncure <merlin.moncure@rcsonline.com>
0 siblings, 1 reply; 20+ messages in thread
From: Merlin Moncure @ 2004-08-11 16:37 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql@mohawksoft.com; pgsql-performance
> 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%.
>
> This concurs with my personal experience.
I'm really curious to see if you guys have compared insert performance
results between 7.4 and 8.0. As you probably know the system sync()
call was replaced with a looping fsync on open file handles. This may
have some interesting interactions with the WAL sync method.
What caught my attention initially was the 300+/sec insert performance.
On 8.0/NTFS/fsync=on, I can't break 100/sec on a 10k rpm ATA disk. My
hardware seems to be more or less in the same league as psql's, so I was
naturally curious if this was a NT/Unix issue, a 7.4/8.0 issue, or a
combination of both.
A 5ms seek time disk would be limited to 200 transaction commits/sec if
each transaction commit has at least 1 seek. Are there some
circumstances where a transaction commit does not generate a physical
seek?
Maybe ext3 is not the worst filesystem after all!
Merlin
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-08-11 17:14 pgsql@mohawksoft.com
parent: Merlin Moncure <merlin.moncure@rcsonline.com>
0 siblings, 1 reply; 20+ messages in thread
From: pgsql@mohawksoft.com @ 2004-08-11 17:14 UTC (permalink / raw)
To: Merlin Moncure <merlin.moncure@rcsonline.com>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-performance
>> 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%.
>>
>> This concurs with my personal experience.
>
> I'm really curious to see if you guys have compared insert performance
> results between 7.4 and 8.0. As you probably know the system sync()
> call was replaced with a looping fsync on open file handles. This may
> have some interesting interactions with the WAL sync method.
>
> What caught my attention initially was the 300+/sec insert performance.
> On 8.0/NTFS/fsync=on, I can't break 100/sec on a 10k rpm ATA disk. My
> hardware seems to be more or less in the same league as psql's, so I was
> naturally curious if this was a NT/Unix issue, a 7.4/8.0 issue, or a
> combination of both.
The system on which I can get 300 inserts per second is a battery backed
up XEON system with 512M RAM, a Promise PDC DMA ATA card, and some fast
disks with write caching enabled.
(We are not worried about write caching because we have a UPS. Since all
non-redundent systems are evaluated on probability of error, we decided
that the probability of power failure and UPS failure was sufficiently
more rare than system crash with file system corruption or hard disk
failure.)
>
> A 5ms seek time disk would be limited to 200 transaction commits/sec if
> each transaction commit has at least 1 seek. Are there some
> circumstances where a transaction commit does not generate a physical
> seek?
>
> Maybe ext3 is not the worst filesystem after all!
>
> Merlin
>
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: [HACKERS] fsync vs open_sync
@ 2004-08-11 20:51 Steve Bergman <steve@rueb.com>
parent: Josh Berkus <josh@agliodbs.com>
1 sibling, 0 replies; 20+ messages in thread
From: Steve Bergman @ 2004-08-11 20:51 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: Merlin Moncure <merlin.moncure@rcsonline.com>; pgsql-performance
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, whereas the penalty
> for ReiserFS and JFS was less than 10%.
>
> This concurs with my personal experience.
>
Yes, I have been wondering about the relative trade offs between
underlying file systems and pgsql.
For metadata journalled filesystems, wouldn't fdatasync be a better
option, since the fs is journalling the metadata anyway?
With its default settings (data=ordered), ext3 is making a guaranty that
after a crash, the filesystem will not only be in a consistent state,
but the files (including the WAL) will not contain garbage, though their
contents may not be the latest. With reiserfs and JFS, files can
contain garbage. (I'm not sure what the implications of all this for
pgsql are.)
And wouldn't the following comparisons with ext3 be more interesting:
ext3,data=writeback,fdatasync vs Other_Journalled_FS,fdatasync
or
ext3,data=journal,open_sync vs Other_Journalled_FS,fdatasync
Just wondering.
-Steve
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: [HACKERS] fsync vs open_sync
@ 2004-08-12 00:06 Gaetano Mendola <mendola@bigfoot.com>
parent: pgsql@mohawksoft.com
0 siblings, 0 replies; 20+ messages in thread
From: Gaetano Mendola @ 2004-08-12 00:06 UTC (permalink / raw)
To: pgsql-performance
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
pgsql@mohawksoft.com 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
|>>about 2500 inserts per second.
|>
|>You are getting 300-400 inserts/sec with fsync on? If you don't mind me
|>asking, what's your hardware? (also, have you checked fsync on #s with
|>the new bgwriter in 7.5?)
|>
|
|
| 300 inserts persecond with fsync on using fdatasync. 2500 inserts per
| second with fsync on using open_sync.
|
| [mwoodward@penguin-021 mwoodward]$ cat /proc/cpuinfo
| processor : 0
| vendor_id : GenuineIntel
| cpu family : 15
| model : 2
| model name : Intel(R) Xeon(TM) CPU 2.40GHz
| stepping : 5
| cpu MHz : 2399.373
| cache size : 512 KB
| fdiv_bug : no
| hlt_bug : no
| f00f_bug : no
| coma_bug : no
| fpu : yes
| fpu_exception : yes
| cpuid level : 2
| wp : yes
| flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
| cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
| bogomips : 4784.12
|
| Linux node1 2.4.25 #1 Mon Mar 22 13:33:41 EST 2004 i686 i686 i386 GNU/Linux
|
| ide2: BM-DMA at 0xc400-0xc407, BIOS settings: hde:pio, hdf:pio
| hde: Maxtor 6Y200P0, ATA DISK drive
| hde: attached ide-disk driver.
| hde: host protected area => 1
| hde: 398297088 sectors (203928 MB) w/7936KiB Cache, CHS=24792/255/63,
| UDMA(100)
|
| PDC20268: IDE controller at PCI slot 06:05.0
I did some experiments too:
inserting 10000 rows in a table with an integer column:
fsync=false ====> ~7.5 secs 1300 insert/sec
wal_sync_method=fsync ====> ~15.5 secs 645 insert/sec
wal_sync_method=fdatasync ====> ~15.5 secs 645 insert/sec
wal_sync_method=open_sync ====> ~10.0 secs 1000 insert/sec
wal_sync_method=open_datasync ====> <the server doesn't start>
Test bed: Postgresql 8.0beta1, linux kernel 2.4.22,
~ hda: IC35L060AVVA07-0, ATA DISK drive
~ hda: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=7476/255/63, UDMA(100)
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 6
cpu MHz : 877.500
cache size : 256 KB
physical id : 0
siblings : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
runqueue : 0
bogomips : 1749.81
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 6
cpu MHz : 877.500
cache size : 256 KB
physical id : 0
siblings : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
runqueue : 1
bogomips : 1749.81
Regards
Gaetano Mendola
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBGrSE7UpzwH2SGd4RAoXnAKCHhuw/pWKgY+OD3JcWYMTPDbmgZwCgyqfT
+OugUEvUF8usYYrWSGDAnn4=
=FAaI
-----END PGP SIGNATURE-----
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-08-13 16:06 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
parent: pgsql@mohawksoft.com
0 siblings, 0 replies; 20+ messages in thread
From: Pierre-Frédéric Caillaud @ 2004-08-13 16:06 UTC (permalink / raw)
To: pgsql-performance
>> What caught my attention initially was the 300+/sec insert performance.
>> On 8.0/NTFS/fsync=on, I can't break 100/sec on a 10k rpm ATA disk. My
>> hardware seems to be more or less in the same league as psql's, so I was
>> naturally curious if this was a NT/Unix issue, a 7.4/8.0 issue, or a
>> combination of both.
There is also the fact that NTFS is a very slow filesystem, and Linux is
a lot better than Windows for everything disk, caching and IO related. Try
to copy some files in NTFS and in ReiserFS...
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-08-13 19:58 Merlin Moncure <merlin.moncure@rcsonline.com>
0 siblings, 0 replies; 20+ messages in thread
From: Merlin Moncure @ 2004-08-13 19:58 UTC (permalink / raw)
To: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>; +Cc: pgsql-performance
> There is also the fact that NTFS is a very slow filesystem, and
> Linux is
> a lot better than Windows for everything disk, caching and IO related. Try
> to copy some files in NTFS and in ReiserFS...
I'm not so sure I would agree with such a blanket generalization. I find NTFS to be very fast, my main complaint is fragmentation issues...I bet NTFS is better than ext3 at most things (I do agree with you about the cache, thoughO.
I think in very general sense the open source stuff is higher quality but Microsoft benefits from a very tight vertical integration of the system. They added ReadFileScatter and WriteFileScatter to the win32 api specifically to make SQL Server run faster and SQL server is indeed very, very good at i/o.
SQL Server keeps a one file database with blocks collected and written asynchronously. It's a very tight system because they have control over every layer of the system.
Know your enemy.
That said, I think transaction based file I/O is 'the way' and if implemented on Reiser4 faster than I/O methodology than offered on windows/ntfs.
Merlin
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-03 17:08 Merlin Moncure <merlin.moncure@rcsonline.com>
0 siblings, 2 replies; 20+ messages in thread
From: Merlin Moncure @ 2004-09-03 17:08 UTC (permalink / raw)
To: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>; +Cc: pgsql-performance
> > There is also the fact that NTFS is a very slow filesystem, and
> > Linux is
> > a lot better than Windows for everything disk, caching and IO related.
> Try
> > to copy some files in NTFS and in ReiserFS...
>
> I'm not so sure I would agree with such a blanket generalization. I find
> NTFS to be very fast, my main complaint is fragmentation issues...I bet
> NTFS is better than ext3 at most things (I do agree with you about the
> cache, thoughO.
Ok, you were right. I made some tests and NTFS is just not very good in the general case. I've seen some benchmarks for Reiser4 that are just amazing.
Merlin
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-03 18:24 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
parent: Merlin Moncure <merlin.moncure@rcsonline.com>
1 sibling, 1 reply; 20+ messages in thread
From: Pierre-Frédéric Caillaud @ 2004-09-03 18:24 UTC (permalink / raw)
To: Merlin Moncure <merlin.moncure@rcsonline.com>; +Cc: pgsql-performance
>> > There is also the fact that NTFS is a very slow filesystem, and
>> > Linux is
>> > a lot better than Windows for everything disk, caching and IO related.
>> Try
>> > to copy some files in NTFS and in ReiserFS...
>>
>> I'm not so sure I would agree with such a blanket generalization. I
>> find
>> NTFS to be very fast, my main complaint is fragmentation issues...I bet
>> NTFS is better than ext3 at most things (I do agree with you about the
>> cache, thoughO.
>
> Ok, you were right. I made some tests and NTFS is just not very good in
> the general case. I've seen some benchmarks for Reiser4 that are just
> amazing.
As a matter of fact I was again amazed today.
I was looking into a way to cache database queries for a website (not
yet) written in Python. The purpose was to cache long queries like those
used to render forum pages (which is the typical slow query, selecting
from a big table where records are rather random and LIMIT is used to cut
the result in pages).
I wanted to save a serialized (python pickled) representation of the data
to disk to avoid reissuing the query every time.
In the end it took about 1 ms to load or save the data for a page with 40
posts... then I wondered, how much does it take just to read or write the
file ?
ReiserFS 3.6, Athlon XP 2.5G+, 512Mb DDR400
7200 RPM IDE Drive with 8MB Cache
This would be considered a very underpowered server...
22 KB files, 1000 of them :
open(), read(), close() : 10.000 files/s
open(), write(), close() : 4.000 files/s
This is quite far from database FS activity, but it's still amazing,
although the disk doesn't even get used. Which is what I like in Linux.
You can write 10000 files in one second and the HDD is still idle... then
when it decides to flush it all goes to disk in one burst.
I did make benchmarks some time ago and found that what sets Linux apart
from Windows in terms of filesystems is :
- very high performance filesystems like ReiserFS
This is the obvious part ; although with a huuuuge amount of data in
small files accessed randomly, ReiserFS is faster but not 10x, maybe
something like 2x NTFS. I trust Reiser4 to offer better performance, but
not right now. Also ReiserFS lacks a defragmenter, and it gets slower
after 1-2 years (compared to 1-2 weeks with NTFS this is still not that
bad, but I'd like to defragment and I cant). Reiser4 will fix that
apparently with background defragger etc.
- caching.
Linux disk caching is amazing. When copying a large file to the same disk
on Windows, the drive head swaps a lot, like the OS can't decide between
reading and writing. Linux, on the other hand, reads and writes by large
chunks and loses a lot less time seekng. Even when reading two files at
the same time, Linux reads ahead in large chunks (very little performance
loss) whereas Windows seeks a lot. The read-ahead and write-back thus gets
it a lot faster than 2x NTFS for everyday tasks like copying files,
backing up, making archives, grepping, serving files, etc...
My windows box was able to saturate a 100Mbps ethernet while serving one
large FTP file on the LAN (not that impressive, it's only 10 MB/s hey!).
However, when several simultaneous clients were trying to download
different files which were not in the disk cache, all hell broke loose :
lots of seeking, and bandwidth dropped to 30 Mbits/s. Not enough
read-ahead...
The Linux box, serving FTP, with half the RAM (256 Mb), had no problem
pushing the 100 Mbits/s with something like 10 simultaneous connections.
The amusing part is that I could not use the Windows box to test it
because it would choke at such a "high" IO concurrency (writing 10
MBytes/s to several files at once, my god).
Of course the files which had been downloaded to the Windows box were cut
in as many fragments as the number of disk seeks during the download...
several hundred fragments each... my god...
What amazes me is that it must just be some parameter somewhere and the
Microsoft guys probably could have easily changed the read-ahead
thresholds and time between seeks when in a multitasking environment, but
they didn't. Why ?
Thus people are forced to buy 10000RPM SCSI drives for their LAN servers
when an IDE raid, used with Linux, could push nearly a Gigabit...
For database, this is different, as we're concerned about large files,
and fsync() times... but it seems reiserfs still wins over ext3 so...
About NTFS vs EXT3 : ext3 dies if you put a lot of files in the same
directory. It's fast but still outperformed by reiser.
I saw XFS fry eight 7 harddisk RAID bays. The computer was rebooted with
the Reset button a few times because a faulty SCSI cable in the eighth
RAID bay was making it hang. The 7 bays had no problem. When it went back
up, all the bays were in mayhem. XFSrepair just vomited over itself and we
got plenty of files with random data in them. Fortunately there was a
catalog of files with their checksums so at least we could know which
files were okay. Have you tried restoring that amount of data from a
backup ?
Now maybe this was just bad luck and crap hardware, but I still won't
touch XFS. Amazing performance on large files though...
I've had my computers shutdown violently by power failures and no
reiserfs problems so far. NTFS is very crash proof too. My windows machine
bluescreens twice a day and still no data loss ;)
Upside : an junkyard UPS with dead batteries, powered with two brand new
12V car batteries, costs 70 euro and powers a computer for more than 5
hours...
Downside :
- it's ugly (I hide it under my desk)
- you "borrow" a battery to start your friend's car, and just five
minutes later, the UPS wants to test itself, discovered it has no more
batteries, and switches everything off... argh.
Good evening...
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-04 10:43 Gaetano Mendola <mendola@bigfoot.com>
parent: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
0 siblings, 2 replies; 20+ messages in thread
From: Gaetano Mendola @ 2004-09-04 10:43 UTC (permalink / raw)
To: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
Pierre-Frédéric Caillaud wrote:
> 22 KB files, 1000 of them :
> open(), read(), close() : 10.000 files/s
> open(), write(), close() : 4.000 files/s
>
> This is quite far from database FS activity, but it's still
> amazing, although the disk doesn't even get used. Which is what I like
> in Linux. You can write 10000 files in one second and the HDD is still
> idle... then when it decides to flush it all goes to disk in one burst.
You can not trust your data in this.
> I've had my computers shutdown violently by power failures and no
> reiserfs problems so far. NTFS is very crash proof too. My windows
> machine bluescreens twice a day and still no data loss ;)
If you have the BSOD twice a day then you have a broken driver or broken
HW. CPU overclocked ?
I understood from your email that you are a Windows haters, try to post
something here:
http://ihatelinux.blogspot.com/
:-)
Regards
Gaetano Mendola
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-05 02:46 Cott Lang <cott@internetstaff.com>
parent: Gaetano Mendola <mendola@bigfoot.com>
1 sibling, 0 replies; 20+ messages in thread
From: Cott Lang @ 2004-09-05 02:46 UTC (permalink / raw)
To: pgsql-performance
Another possibly useless datapoint on this thread for anyone who's
curious ... open_sync absolutely stinks over NFS at least on Linux. :)
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-05 03:47 Christopher Browne <cbbrowne@acm.org>
parent: Merlin Moncure <merlin.moncure@rcsonline.com>
1 sibling, 2 replies; 20+ messages in thread
From: Christopher Browne @ 2004-09-05 03:47 UTC (permalink / raw)
To: pgsql-performance
The world rejoiced as merlin.moncure@rcsonline.com ("Merlin Moncure") wrote:
> Ok, you were right. I made some tests and NTFS is just not very
> good in the general case. I've seen some benchmarks for Reiser4
> that are just amazing.
Reiser4 has been sounding real interesting.
The killer problem is thus:
"We must caution that just as Linux 2.6 is not yet as stable as
Linux 2.4, it will also be some substantial time before V4 is as
stable as V3."
In practice, there's a further problem.
We have some systems at work we need to connect to EMC disk arrays;
that's something that isn't supported by EMC unless you're using a
whole set of pieces that are "officially supported."
RHAT doesn't want to talk to you about support for anything other than
ext3.
I'm not sure what all SuSE supports; they're about the only other Linx
vendor that EMC would support, and I don't expect that Reiser4 yet
fits into the "supportable" category :-(.
The upshot of that is that this means that we'd only consider using
stuff like Reiser4 on "toy" systems, and, quite frankly, that means
that they'll have "toy" disk as opposed to the good stuff :-(.
And frankly, we're too busy with issues nearer to our hearts than
testing out ReiserFS. :-(
--
output = ("cbbrowne" "@" "cbbrowne.com")
http://cbbrowne.com/info/emacs.html
"Linux! Guerrilla Unix Development Venimus, Vidimus, Dolavimus."
-- <mah@ka4ybr.com> Mark A. Horton KA4YBR
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-05 05:16 Steve Bergman <steve@rueb.com>
parent: Christopher Browne <cbbrowne@acm.org>
1 sibling, 1 reply; 20+ messages in thread
From: Steve Bergman @ 2004-09-05 05:16 UTC (permalink / raw)
To: Christopher Browne <cbbrowne@acm.org>; +Cc: pgsql-performance
On Sat, 2004-09-04 at 23:47 -0400, Christopher Browne wrote:
> The world rejoiced as merlin.moncure@rcsonline.com ("Merlin Moncure") wrote:
> > Ok, you were right. I made some tests and NTFS is just not very
> > good in the general case. I've seen some benchmarks for Reiser4
> > that are just amazing.
>
> Reiser4 has been sounding real interesting.
>
Are these independent benchmarks, or the benchmarketing at namesys.com?
Note that the APPEND, MODIFY, and OVERWRITE phases have been turned off
on the mongo tests and the other tests have been set to a lexical (non
default for mongo) mode. I've done some mongo benchmarking myself and
reiser4 loses to ext3 (data=ordered) in the excluded tests. APPEND
phase performance is absolutely *horrible*. So they just turned off the
phases in which reiser4 lost and published the remaining results as
proof that "resier4 is the fastest filesystem".
See: http://marc.theaimsgroup.com/?l=reiserfs&m=109363302000856
-Steve Bergman
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-05 11:41 Geoffrey <esoteric@3times25.net>
parent: Christopher Browne <cbbrowne@acm.org>
1 sibling, 1 reply; 20+ messages in thread
From: Geoffrey @ 2004-09-05 11:41 UTC (permalink / raw)
To: pgsql-performance
Christopher Browne wrote:
> I'm not sure what all SuSE supports; they're about the only other Linx
> vendor that EMC would support, and I don't expect that Reiser4 yet
> fits into the "supportable" category :-(.
I use quite a bit of SuSE, and although I don't know their official
position on Reiser file systems, I do know that it is the default when
installing, so I'd suggest you might check into it.
--
Until later, Geoffrey Registered Linux User #108567
AT&T Certified UNIX System Programmer - 1995
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-05 18:01 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
parent: Gaetano Mendola <mendola@bigfoot.com>
1 sibling, 0 replies; 20+ messages in thread
From: Pierre-Frédéric Caillaud @ 2004-09-05 18:01 UTC (permalink / raw)
To: pgsql-performance
Were you upset by my message ? I'll try to clarify.
> I understood from your email that you are a Windows haters
Well, no, not really. I use Windows everyday and it has its strengths. I
still don't think the average (non-geek) person can really use Linux as a
Desktop OS. The problem I have with Windows is that I think it could be
made much faster, without too much effort (mainly some tweaking in the
Disk IO field), but Microsoft doesn't do it. Why ? I can't understand this.
>> in Linux. You can write 10000 files in one second and the HDD is still
>> idle... then when it decides to flush it all goes to disk in one burst.
>
> You can not trust your data in this.
That's why I mentioned that it did not relate to database type
performance. If the computer crashes while writing these files, some may
be partially written, some not at all, some okay... the only certainty is
about filesystem integrity. But it's exactly the same on all Journaling
filesystems (including NTFS). Thus, with equal reliability, the faster
wins. Maybe, with Reiser4, we will see real filesystem transactions and
maybe this will translate in higher postgres performance...
>
>> I've had my computers shutdown violently by power failures and no
>> reiserfs problems so far. NTFS is very crash proof too. My windows
>> machine bluescreens twice a day and still no data loss ;)
>
> If you have the BSOD twice a day then you have a broken driver or broken
> HW. CPU overclocked ?
I think this machine has crap hardware. In fact this example was to
emphasize the reliability of NTFS : it is indeed remarkable that no data
loss occurs even on such a crap machine. I know Windows has got quite
reliable now.
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-05 18:03 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
parent: Geoffrey <esoteric@3times25.net>
0 siblings, 0 replies; 20+ messages in thread
From: Pierre-Frédéric Caillaud @ 2004-09-05 18:03 UTC (permalink / raw)
To: pgsql-performance
I trust ReiserFS 3.
I wouldn't trust the 4 before maybe 1-2 years.
On Sun, 05 Sep 2004 07:41:29 -0400, Geoffrey <esoteric@3times25.net> wrote:
> Christopher Browne wrote:
>
>> I'm not sure what all SuSE supports; they're about the only other Linx
>> vendor that EMC would support, and I don't expect that Reiser4 yet
>> fits into the "supportable" category :-(.
>
> I use quite a bit of SuSE, and although I don't know their official
> position on Reiser file systems, I do know that it is the default when
> installing, so I'd suggest you might check into it.
>
>
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: fsync vs open_sync
@ 2004-09-09 17:12 Mark Wong <markw@osdl.org>
parent: Steve Bergman <steve@rueb.com>
0 siblings, 0 replies; 20+ messages in thread
From: Mark Wong @ 2004-09-09 17:12 UTC (permalink / raw)
To: Steve Bergman <steve@rueb.com>; +Cc: Christopher Browne <cbbrowne@acm.org>; pgsql-performance
On Sun, Sep 05, 2004 at 12:16:42AM -0500, Steve Bergman wrote:
> On Sat, 2004-09-04 at 23:47 -0400, Christopher Browne wrote:
> > The world rejoiced as merlin.moncure@rcsonline.com ("Merlin Moncure") wrote:
> > > Ok, you were right. I made some tests and NTFS is just not very
> > > good in the general case. I've seen some benchmarks for Reiser4
> > > that are just amazing.
> >
> > Reiser4 has been sounding real interesting.
> >
>
> Are these independent benchmarks, or the benchmarketing at namesys.com?
> Note that the APPEND, MODIFY, and OVERWRITE phases have been turned off
> on the mongo tests and the other tests have been set to a lexical (non
> default for mongo) mode. I've done some mongo benchmarking myself and
> reiser4 loses to ext3 (data=ordered) in the excluded tests. APPEND
> phase performance is absolutely *horrible*. So they just turned off the
> phases in which reiser4 lost and published the remaining results as
> proof that "resier4 is the fastest filesystem".
>
> See: http://marc.theaimsgroup.com/?l=reiserfs&m=109363302000856
>
>
> -Steve Bergman
>
>
>
Reiser4 also isn't optmized for lots of fsyncs (unless it's been done
recently.) I believe the mention fsync performance in their release
notes. I've seen this dramatically hurt performance with our OLTP
workload.
--
Mark Wong - - markw@osdl.org
Open Source Development Lab Inc - A non-profit corporation
12725 SW Millikan Way - Suite 400 - Beaverton, OR 97005
(503) 626-2455 x 32 (office)
(503) 626-2436 (fax)
http://developer.osdl.org/markw/
^ permalink raw reply [nested|flat] 20+ messages in thread
end of thread, other threads:[~2004-09-09 17:12 UTC | newest]
Thread overview: 20+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-08-10 15:25 Re: [HACKERS] fsync vs open_sync Merlin Moncure <merlin.moncure@rcsonline.com>
2004-08-10 15:54 ` pgsql@mohawksoft.com
2004-08-12 00:06 ` Gaetano Mendola <mendola@bigfoot.com>
2004-08-10 17:18 ` Josh Berkus <josh@agliodbs.com>
2004-08-10 18:04 ` pgsql@mohawksoft.com
2004-08-11 20:51 ` Steve Bergman <steve@rueb.com>
2004-08-11 16:37 Re: fsync vs open_sync Merlin Moncure <merlin.moncure@rcsonline.com>
2004-08-11 17:14 ` pgsql@mohawksoft.com
2004-08-13 16:06 ` Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
2004-08-13 19:58 Re: fsync vs open_sync Merlin Moncure <merlin.moncure@rcsonline.com>
2004-09-03 17:08 Re: fsync vs open_sync Merlin Moncure <merlin.moncure@rcsonline.com>
2004-09-03 18:24 ` Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
2004-09-04 10:43 ` Gaetano Mendola <mendola@bigfoot.com>
2004-09-05 02:46 ` Cott Lang <cott@internetstaff.com>
2004-09-05 18:01 ` Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
2004-09-05 03:47 ` Christopher Browne <cbbrowne@acm.org>
2004-09-05 05:16 ` Steve Bergman <steve@rueb.com>
2004-09-09 17:12 ` Mark Wong <markw@osdl.org>
2004-09-05 11:41 ` Geoffrey <esoteric@3times25.net>
2004-09-05 18:03 ` Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
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