dualvsta | Born To Be Free a écrit :
Extrait du manuel 8.0.2 en anglais, répondra a une partie de tes interrogations coté Hard
Spoiler :
1.1 Hardware Requirements
Since FreeNAS™ 8.0.2 is based on FreeBSD 8.2, it supports the same hardware found in the FreeBSD
8.2 Hardware Compatability List.
Actual hardware requirements will vary depending upon what you are using your FreeNAS™ system
for. This section provides some guidelines to get you started. You should also skim through the
FreeNAS™ Hardware Forum for performance tips from other FreeNAS™ users. The Hardware Forum
is also an excellent place to post questions regarding your hardware setup or the hardware best suited to
meet your requirements.
1.1.1 Architecture
While FreeNAS™ is available for both 32-bit and 64-bit architectures, you should use 64-bit hardware
if you care about speed or performance. A 32-bit system can only address up to 4GB of RAM, making
it poorly suited to the RAM requirements of ZFS. If you only have access to a 32-bit system, consider
using UFS instead of ZFS.
1.1.2 RAM
The best way to get the most out of your FreeNAS™ system is to install as much RAM as possible. If
your RAM is limited, consider using UFS until you can afford better hardware. ZFS typically requires a
minimum of 6 GB of RAM in order to provide good performance; in practical terms (what you can
actually install), this means that the minimum is really 8 GB. The more RAM, the better the
performance, and the Forums provide anecdotal evidence from users on how much performance is
gained by adding more RAM. For systems with large disk capacity (greater than 6 TB), a general rule
of thumb is 1GB of RAM for every 1TB of storage.
NOTE: by default, ZFS disables pre-fetching (caching) for systems containing less than 4 GB of
usable RAM. Not using pre-fetching can really slow down performance. 4 GB of usable RAM is not
the same thing as 4 GB of installed RAM as the operating system resides in RAM. This means that the
practical pre-fetching threshold is 6 GB, or 8 GB of installed RAM. You can still use ZFS with less
RAM, but performance will be affected.
If you are installing FreeNAS™ on a headless system, disable the shared memory settings for the video
card in the BIOS.
1.1.3 Compact or USB Flash
The FreeNAS™ operating system is a running image that needs to be installed onto a USB or compact
flash device that is at least 2 GB in size. A list of compact flash drives known to work with FreeNAS™
can be found on the .7 wiki. If you don't have compact flash, you can instead use a USB thumb drive
that is dedicated to the running image and which stays inserted in the USB slot. While technically you
can install FreeNAS™ onto a hard drive, this is discouraged as you will lose the storage capacity of the
drive. In other words, the operating system will take over the drive and will not allow you to store data
on it, regardless of the size of the drive.
The FreeNAS™ installation will partition the operating system drive into two ~1GB partitions. One
partition holds the current operating system and the other partition is used when you upgrade. This
allows you to safely upgrade to a new image or to revert to an older image should you encounter
problems.
1.1.4 Storage Disks and Controllers
The Disk section of the FreeBSD Hardware List lists the supported disk controllers. In addition,
support for 3ware 6gbps RAID controllers has been added along with the CLI utility tw_cli for
managing 3ware RAID controllers.
FreeNAS™ supports hot pluggable drives. Make sure that AHCI is enabled in the BIOS.
If you have some money to spend and wish to optimize your disk subsystem, consider your read/write
needs, your budget, and your RAID requirements.
For example, moving the the ZIL (ZFS Intent Log) to a dedicated SSD only helps performance if you
have synchronous writes, like a database server. SSD cache devices only help if your working set is
larger than system RAM, but small enough that a significant percentage of it will fit on the SSD.
If you have steady, non-contiguous writes, use disks with low seek times. Examples are 10K or 15K
SAS drives which cost about $1/GB. An example configuration would be six 15K SAS drives in a
RAID 10 which would yield 1.8 TB of usable space or eight 15K SAS drives in a RAID 10 which
would yield 2.4 TB of usable space.
7200 RPM SATA disks are designed for single-user sequential I/O and are not a good choice for multiuser
writes.
If you have the budget and high performance is a key requirement, consider a Fusion-I/O card which is
optimized for massive random access. These cards are expensive and are suited for high end systems
that demand performance. A Fusion-I/O can be formatted with a filesystem and used as direct storage;
when used this way, it does not have the write issues typically associated with a flash device. A Fusion-
I/O can also be used as a cache device when your ZFS dataset size is bigger than your RAM. Due to the
increased throughput, systems running these cards typically use multiple 10 GigE network interfaces.
If you will be using ZFS, Disk Space Requirements for ZFS Storage Pools recommends a minimum of
16 GB of disk space. Due to the way that ZFS creates swap, you can not format less than 3GB of space
with ZFS. However, on a drive that is below the minimum recommended size you lose a fair amount of
storage space to swap: for example, on a 4 GB drive, 2GB will be reserved for swap.
If you are new to ZFS and are purchasing hardware, read through ZFS Storage Pools
Recommendations first.
1.1.5 Network Interfaces
The FreeBSD Ethernet section of the Hardware Notes indicates which interfaces are supported by each
driver. While many interfaces are supported, FreeNAS™ users have seen the best performance from
Intel and Chelsio interfaces, so consider these brands if you are purchasing a new interface.
At a minimum you will want to use a GigE interface. While GigE interfaces and switches are
affordable for home use, it should be noted that modern disks can easily saturate 110 MB/s. If you
require a higher network throughput, you can "bond" multiple GigE cards together using the LACP
type of Link Aggregation. However, any switches will need to support LACP which means you will
need a more expensive managed switch rather than a home user grade switch.
If network performance is a requirement and you have some money to spend, use 10 GigE interfaces
and a managed switch. If you are purchasing a managed switch, consider one that supports LACP and
jumbo frames as both can be used to increase network throughput.
NOTE: at this time the following are not supported: InfiniBand, FibreChannel over Ethernet, or
wireless interfaces.
If network speed is a requirement, consider both your hardware and the type of shares that you create.
On the same hardware, CIFS will be slower than FTP or NFS as Samba is single-threaded. If you will
be using CIFS, use a fast CPU.
|
|
Farfyboom a écrit :
Pour faire plus court, si tu fais pas de grosse grappe ZFS et que tu n'utilises pas les dernières versions de FreeNAS, je dirais que c'est OK. Il faudrait juste booster un peu la quantité de RAM car 1GB c'est un peu too short!
Pour info, je fais parfaitement tourner une grappe RAIDZ1 (sans encryptage) avec la config suivante:
FreeNAS 0.7.2 avec ZFS v13
AMD Turion64 MT32
3*1TB Western Digital Green
3GB de RAM (1 GB de RAM par TB de stockage)
Alim fanless 120W
Interface Gb Ethernet Nforce MCP6
Je ne jouis pas des toutes dernières fonctionnalités (dernières versions de ZFS notamment) mais le serveur est très stable et suffisamment performant pour une utilisation intensive : partage SAMBA/CIFS avec débits corrects (50MB/s en moyenne), serveur UPnP, daemon transmission avec partage H24, synchronisation de fichiers rSync, serveur FTP...
|
the_matrix_has_you a écrit :
L'adaptateur compact flash -> IDE est une excellente solution, par contre carte compact flash de 4Go minimum pour les versions de FreeNAS supérieur à la 8.0.3 (la release actuelle est la 8.2)
Pour les performances FarFyboom a parfaitement répondu, tu peux même mettre une 8.2, tant que tu n'utilises pas la compression des données sur le pool, le proc n'est pas beaucoup sollicité. Encore moins si tu montes les disques en miroir par rapport à un RAIDZ1.
Sinon sans ajouter de RAM tu peux utiliser l'UFS, mais c'est un peu dommage de se priver de ZFS à mon avis.
|
Farfyboom a écrit :
Ouaip, j'ai oublié de le dire mais j'utilise moi aussi une carte CF 4Go Kingston sur adaptateur P-ATA et c'est au poil! Il faut juste s'assurer de prendre une CF bootable (compatible UDMA6) et d'en prendre une suffisamment robuste et performante, pas une noname de merde quoi. Celles qui sont faite pour les appareils photos Reflex haut de gamme font parfaitement l'affaire en général.
Le bousin est plutôt vorace en RAM et pas trop en CPU... Donc pour ce qui est de monter un pool ZFS de 3 ou 4 disques avec un Sempron AM2, je pense que ça devrait passer finger in ze nose si pas d'encryptage (bouffe du CPU à mort). La compression elle varie selon l'algorithme, dans ce cas choisir lzjb qui est pas trop gourmand.
|
Et bien merci bien, je vais remonter la config dans un boitier pourri que j'ai en stock. Si tout marche bien, j'achèterais un beau Fractal.
En fouillant, j'ai retrouvé 2 Go de DDR2 supplémentaire donc ça devrait le faire.
Je vais acheter une petite compact flash, je n'ai que des 2 Go ici. Je vais faire attention a vos recommandation.
Je comptais faire un raidz1 de 3x1 To mais j'ai pas très bien compris si il faut un 4 ieme disque pour cela.
Je reviendrais surement tres vite si l'ordi a résisté aux coups de machète en cas de message d'erreur
|