Linked by David Adams on Wed 24th Sep 2008 22:44 UTC, submitted by snydeq
Thread beginning with comment 331390
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2005-07-12
I'll pick ZFS as an example to challenge. It's a memory hog. It's a CPU hog. It has no place on any of the machines in my house, which all run ext3 reliably and nicely. Where might it be useful?
You don't happen to be running ZFS with FUSE so it runs in user land are you? Perhaps if Linux wasn't so antagonistic to anything none-GPL then perhaps they could include it in the kernel. Performance would increase dramatically.
ZFS is awesome for data centers, file repositories and server farms. It provides redundancy and load balancing with absolute ease. "
No he is running solaris maybe on a old system maybe 32bit? Oh thats right SUN has had 64bit for the last ten years... So maybe old code isnt that great ZFS shouldnt work in 32bit in my opinion it should probably be run on 128bit procs that haven't been developed yet (since its a 128bit filesystem)