eric kustarz <[EMAIL PROTECTED]> wrote:
> Ben Rockwood wrote:
> I imagine what's happening is that tar is a single-threaded application
> and it's basically doing: open, asynchronous write, close. This will go
> really fast locally. But for NFS due to the way it does cache
> consistency, on CLOSE, it must make sure that the writes are on stable
> storage, so it does a COMMIT, which basically turns your asynchronous
> write into a synchronous write. Which means you basically have a
> single-threaded app doing synchronous writes- ~ 1/2 disk rotational
> latency per write.
star does write files in a way that grants consistency, GNU tar and
Sun tar do not.
If you like to see the difference, you may try to compare a
star x
with star x -no-fsync
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
