Linked by Rahul on Mon 13th Oct 2008 21:19 UTC
Permalink for comment 333998
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
More News »
Sponsored Links



Member since:
2005-07-07
Ok. So from the articles, we can say that ZFS scales all the way down to 4GB of memory and an AMD Athlon X2 BE-2350 dual core processor running in 64 bit mode. "
No, People are running ZFS on 512MB boxes. People are also running them in VMWare VMs. Zfs-on-FUSE is used on linux there are numerous articles if you search.
People put a boatload of memory because ZFS performs best when it can cache a lot. I fail to see how you can misconstrue that to mean it needs a lot of memory. Less memory won't give you the best throughput.
http://www.opensolaris.org/jive/thread.jspa?threadID=73990&tstart=-...
There are posts here where people having been using ZFS with 512MB.
"My home ZFS server runs with only 1 GB of RAM. It achieves 430 MB/s sequential
reads and 220 MB/s writes. This is very good, given that its primary task is
to serve large files over NFS."
"speed" is another vague term. Do you mean throughput, or latency. Local I/O,
or over NFS. Etc. FYI a small amount of RAM usually impacts random I/O
workloads when they would otherwise fit in memory, but does not reduce the
throughput of sequential I/O because prefetching algorithms work just fine as
all they need is a few tens of MB of memory.
..........
As a matter of fact, until march 2008 I had been running snv_55b for over a
year with only 512 MB to serve a 2.0-TB pool over NFS. Again, the performances
(throughput) were very acceptable. If that's what the OP needs, then 512 MB
would be *technically* sufficient, even if given the current prices 1 GB would
make more sense.
-marc
"