Hello all,
Just got FreeNAS installed on my ESXi 5.1 server. Right now it is just hosts FreeNAS and a Debian box. The box itself is an ASRock Vision3D that used to be an HTPC, but is now re-purposed as a home server. Here are the short specs:
i3 CPU
8GB memory (mobo only supports a max of 8GB)
SansDigital TR4UTBPN with 4x 3tb WD Red (12TB raw) in JBOD
My plan is:
1. Debian machine hosts small (7player) minecraft server, small ventrilo server, and uTorrent.
2. FreeNAS gets the SansDigital to itself and runs RaidZ1
3. The Debian box will host / download various open source software onto the FreeNAS box over an internal virtual network.
4. FreeNAS will also be a standard home CIFS filer / media streamer over the physical NIC.
The Debian box is a very slim build, with no GUI at all, and only the dependencies required for the three applications. I have Minecraft's Java application set to use no more than 1.75GB of memory, but I have never seen it use more than 30% of that, so the entire server typically uses <1GB of memory. The WD Reds haven't come in the mail yet so FreeNAS is just kinda sitting there doing nothing.
Right now memory is allocated like this:
FreeNAS - 5.5GB
Debian - 2GB
Since Debian usually uses such little RAM, I'd like to overcommit memory like this:
FreeNAS - 7 GB
Debian - 2GB
With the overcommitment I will be guaranteed more memory for FreeNAS most of the time, but occasionally run the risk of VMWare paging stuff on the local drive if the Debian performance suddenly exploded at the same time as FreeNAS (unlikely).
For this to work FreeNAS needs a balloon driver, which it looks like it does:
http://support.freenas.org/changeset/02a8b011b9ed4ae48c19219b9518b21cad3cbb56
"372 device virtio_balloon # VirtIO Memory Balloon device"
Thoughts?
Just got FreeNAS installed on my ESXi 5.1 server. Right now it is just hosts FreeNAS and a Debian box. The box itself is an ASRock Vision3D that used to be an HTPC, but is now re-purposed as a home server. Here are the short specs:
i3 CPU
8GB memory (mobo only supports a max of 8GB)
SansDigital TR4UTBPN with 4x 3tb WD Red (12TB raw) in JBOD
My plan is:
1. Debian machine hosts small (7player) minecraft server, small ventrilo server, and uTorrent.
2. FreeNAS gets the SansDigital to itself and runs RaidZ1
3. The Debian box will host / download various open source software onto the FreeNAS box over an internal virtual network.
4. FreeNAS will also be a standard home CIFS filer / media streamer over the physical NIC.
The Debian box is a very slim build, with no GUI at all, and only the dependencies required for the three applications. I have Minecraft's Java application set to use no more than 1.75GB of memory, but I have never seen it use more than 30% of that, so the entire server typically uses <1GB of memory. The WD Reds haven't come in the mail yet so FreeNAS is just kinda sitting there doing nothing.
Right now memory is allocated like this:
FreeNAS - 5.5GB
Debian - 2GB
Since Debian usually uses such little RAM, I'd like to overcommit memory like this:
FreeNAS - 7 GB
Debian - 2GB
With the overcommitment I will be guaranteed more memory for FreeNAS most of the time, but occasionally run the risk of VMWare paging stuff on the local drive if the Debian performance suddenly exploded at the same time as FreeNAS (unlikely).
For this to work FreeNAS needs a balloon driver, which it looks like it does:
http://support.freenas.org/changeset/02a8b011b9ed4ae48c19219b9518b21cad3cbb56
"372 device virtio_balloon # VirtIO Memory Balloon device"
Thoughts?