The system has 2 onboard 1Gpbs nics
I want to turn the system into a NAS.
It looks like the 16GB RAM of the NAS is a waste.
Is there a way to convert most of the content in the extra RAM to cache, or some RAMDRIVE can be used for some extra fast swap space?
The host controller uses Ubuntu.
Which method is the most reliable and relatively simple to set up?
If I use the system RAM of the NAS for some kind of caching, will I see a significant improvement in performance?
< p>For this problem, 16GB is quite a lot of RAM. However, it just fits your needs. It all depends on how much data you have active at any given time. If the “working set” of the active/open file is More than 12GB, then 16GB of RAM is perfect. Ideally, you want all open files to fit into the server cache to provide the best performance. What level depends on your environment, so there is no set answer. /p>
For various reasons, all data fits into RAM, which is good, but one of them is writing. It allows the server to do I/O reordering to minimize HD latency, which is also what RAID cards can do Thing.
I have a 4 CPU 16GB RAM system with Areca 1230 RAID card and 6 HD, with RAID 0 1 configuration, with 1 hot backup .
The system has 2 onboard 1Gpbs nics
I want to turn the system into a NAS.
It looks like the 16GB RAM of the NAS is a waste .
Is there a way to convert most of the extra RAM content into cache, or some RAMDRIVE can be used for some extra fast swap space?
The host controller uses Ubuntu.
Which method is the most reliable and relatively simple to set up?
If I use the system RAM of the NAS for some kind of caching, will I see a significant improvement in performance?
It depends on the service that provides the NAS function. Samba? NFS? all of the above? On this basis, Linux will use all available unallocated memory as file cache. By default, this amount of memory will be used through Linux’s regular caching mechanism. Especially if using a 64-bit kernel.
< p>For this problem, 16GB is quite a lot of RAM. However, it just fits your needs. It all depends on how much data you have active at any given time. If the “working set” of the active/open file is More than 12GB, then 16GB of RAM is perfect. Ideally, you want all open files to fit into the server cache to provide the best performance. What level depends on your environment, so there is no set answer. /p>
For various reasons, all data fits into RAM, which is good, but one of them is writing. It allows the server to do I/O reordering to minimize HD latency, which is also what RAID cards can do Things.