Linked by Thom Holwerda on Fri 23rd Oct 2009 21:13 UTC, submitted by poundsmack
Mac OS X John Siracusa, the Mac OS X guru who writes those insanely detailed and well-written Mac OS X reviews for Ars Technica, once told a story about the evolution of the HFS+ file system in Mac OS X - he said it was a struggle between the Mac guys who wanted the features found in BeOS' BFS, and the NEXT guys who didn't really like these features. In the end, the Mac guys won, and over the course of six years, Mac OS X reached feature parity - and a little more - with the BeOS (at the FS level).
Thread beginning with comment 390784
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by kaiwai
by jwwf on Sat 24th Oct 2009 01:24 UTC in reply to "Comment by kaiwai"
jwwf
Member since:
2006-01-19

The fundamental problem I think people are avoiding to address is ZFS major memory hogging; this might be ok if you have a massive multi-core monster with minimum 2GB memory to get decent performance. That isn't acceptable for a file system that is supposed to 'rule them all' that can scale from an embedded iPhone/iPod Touch device all the way up to a Mac Pro with a high end configuration.


I'd be more willing to agree if it wasn't for personal experience with my core 2 macbook hitting swap every day with 1gb and leopard. It wasn't really usable until I upgraded (to 4gb).

Anyway, I had hoped for ZFS on the Mac, but I'm just as annoyed that they are removing UFS. HFS+ doesn't even support sparse files.

Reply Parent Bookmark Score: 4

RE[2]: Comment by kaiwai
by kaiwai on Sat 24th Oct 2009 01:37 in reply to "RE: Comment by kaiwai"
kaiwai Member since:
2005-07-06

I'd be more willing to agree if it wasn't for personal experience with my core 2 macbook hitting swap every day with 1gb and leopard. It wasn't really usable until I upgraded (to 4gb).


And what you experienced has nothing to do with the HFS+ file system at all. We're talking about ZFS and the memory used to improve performance. It is a known side effect of the file system design - ZFS was never designed to be used in an environment where memory is at a premium.

Anyway, I had hoped for ZFS on the Mac, but I'm just as annoyed that they are removing UFS. HFS+ doesn't even support sparse files.


UFS was a walking disaster area when one considers the litany of issues people had with it. Apple is eventually going to replace it with something that will scale from embedded to servers so that they don't have to have duplication and thus unneeded extra cost. HAMMER will do what you need - are there features missing? of course but HAMMER is in continuous development with the short comings being addressed.

Unlike ZFS, HAMMER provides everything plus a lower memory foot print - I'd say that is a pretty good alternative to ZFS.

Reply Parent Bookmark Score: 4

RE[3]: Comment by kaiwai
by jwwf on Sat 24th Oct 2009 02:31 in reply to "RE[2]: Comment by kaiwai"
jwwf Member since:
2006-01-19

"I'd be more willing to agree if it wasn't for personal experience with my core 2 macbook hitting swap every day with 1gb and leopard. It wasn't really usable until I upgraded (to 4gb).


And what you experienced has nothing to do with the HFS+ file system at all. We're talking about ZFS and the memory used to improve performance. It is a known side effect of the file system design - ZFS was never designed to be used in an environment where memory is at a premium.
"

Of course not. Why would you think that I connect OSX memory usage with HFS+ ? My point is that leopard as deployed on desktop class platforms is _already_ a memory hog in my experience. Thus it's hard for me to speculate on ZFS not making the cut because it _might_ be a memory hog on OSX.

Why should a next gen apple FS be required to span all platforms? This is as likely as not to lead to undesirable compromises on both ends, even if it is cheaper. I say horses for courses. (do we buy apple products because they are cheap or cheap to design? does apple pass cheap design costs on to us?).

"Anyway, I had hoped for ZFS on the Mac, but I'm just as annoyed that they are removing UFS. HFS+ doesn't even support sparse files.


UFS was a walking disaster area when one considers the litany of issues people had with it. Apple is eventually going to replace it with something that will scale from embedded to servers so that they don't have to have duplication and thus unneeded extra cost. HAMMER will do what you need - are there features missing? of course but HAMMER is in continuous development with the short comings being addressed.

Unlike ZFS, HAMMER provides everything plus a lower memory foot print - I'd say that is a pretty good alternative to ZFS.
"

Hammer might be great on OS X except for the fact that it does not currently exist on OS X. I wouldn't bet on that changing either, but would be pleased to be proven wrong.

Reply Parent Bookmark Score: 2

RE[3]: Comment by kaiwai
by Mark Williamson on Sat 24th Oct 2009 13:24 in reply to "RE[2]: Comment by kaiwai"
Mark Williamson Member since:
2005-07-06


Unlike ZFS, HAMMER provides everything plus a lower memory foot print - I'd say that is a pretty good alternative to ZFS.


I'm pretty sure that HAMMER doesn't give you writeable snapshots, which ZFS does - that feature could be very useful for some purposes. For people who just want free or cheap read-only snapshots, HAMMER should satisfy, feature-wise.

Interestingly Matt Dillon (DragonflyBSD lead developer) was considering ZFS for a while but decided it didn't solve the problems he was interested in (he wants to do single system image clustering, i.e. tying a cluster together into a single logical unix system. HAMMER is designed to accommodate that goal in some way).

Reply Parent Bookmark Score: 2