NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Would this type heatsink/fan be suitable for a Readynas Pro 6 (newest version) running OS 6 ?
Hey guys I have already modded my RNDP6000 with Ram, CPU and PSU but I'm now working on changing the CPU fan as I'm not happy with the only temporarily installed and very basic 'Coolmaster' fan. ...
Since I've never had a Pro6 with a quad core processor and have no Pro6 in operation at all at this time, I can't give you specifics. You'll have to experiment. I don't even know what you are seeing right now with that quad-core processor.
But you might want to start by changing the ignore temp3 to this:
label temp3 "CoreX"compute temp3 @%35, @%35Then see what temp1, temp4, etc. do.That @%35 option is non-standard, BTW -- something Netgear apparently added to lm-sensors. But it basically makes the floor of the reading be 35°C, as the internal temperature monitors of CPUs tend to be inaccurate below that threshold.You don't mess with the symbolic link. When you change the target file, the link effectively updates. You may want to keep a copy of the original before you start making changes. You will probably have to at least re-start the readynasd process to see the effect in the GUI, maybe even re-boot.
That's quite an undertaking. I'm wondering what you are doing with your NAS that you felt that a quad-core processor is necessary and whether of not you've realized any real speed improvement. Most of the NAS's standard processes are limited to a single core, so you have to be running a lot of CPU-intensive processes to take advantage of the four cores. And even then, many will be slowed down by multiple processes accessing the RAID simultaneously. On a Pro6, the 800MHz FSB is one of the bottlenecks a faster processor won't overcome, but a faster one does help some. So while a faster CPU (especially on the original Pro with the Pentium Dual E2160 @ 1.80GHz) will help even with standard processes, a quad-core won't typically do much unless you are doing something like transcoding multiple streams simultaneously.
The thing I find slows my NAS down the most is if SMDB reaches 100% of "CPU use" (which is really use of that particular core/thread), and more cores won't help that. What does help is keeping the number of files in any given directory small, as that clearly makes SMDB take less CPU time (still up to 100%, but for a much shorter duration). Defragging might help some, too; but I don't due to the negative impact on snapshot space.
Ditto on the memory, what do you expect to accomplish with more? With just 4GB, I find my NAS using a lot of RAM just for disk buffering. My rack-mount models are more easily upgraded to more than that, and I didn't find any significant improvement, though I also don't have a lot of simultaneous users where it might help more.
Please note I'm not criticizing. I'm interested in informing others of what to expect so they can determine if a mod like this is worthwhile for them.
To be honest, I have been in IT for 40+ years and just wanted to 'tinker' with my NAS a bit...
The quad CPU def has made a difference, especially with PLEX.
I was hoping to upgrade the ram to 2x4gb 1066 (from 800) just have a little more 'oomph!'...for transcoding etc
on a side note, would you recommend utilizing the network "'bond" (in mode "IEEE 802.3ad LACP) option on this NAS ?, as my Asus ROG GT-AX6000 router supports "Bond/Link aggregation"... I'm not sure about this as I have never had the need to implement it , but since its an option, I'm curious...lol
many thanks
ps. oops! forgot to add one pic of the Gelid Heatsink in position....
xlr8r wrote:
on a side note, would you recommend utilizing the network "'bond" (in mode "IEEE 802.3ad LACP) option on this NAS ?, as my Asus ROG GT-AX6000 router supports "Bond/Link aggregation"... I'm not sure about this as I have never had the need to implement it , but since its an option, I'm curious...lol
In general, this doesn't result in much performance gain for most home NAS. It makes a lot more sense when you are deploying in an enterprise where you have lots of PCs accessing the NAS at the same time.
The reason is that with LACP the all traffic going from the NAS to a specific client all goes out the same NIC port. That ensures that the traffic doesn't overrun the client's gigabit connection. Similarly, all the traffic going from a specific client to the NAS also uses the same NIC. The NAS selects the NIC for its outbound traffic, the router will select the NIC for its outbound traffic.
So if (for example) you have two clients, then there is a 50-50 chance that they will share the same NIC when reading from the NAS, and a 50-50 chance that they will share the same NIC when writing to the NAS. So only 1 chance in 4 of getting a performance gain in both directions.
Thanks StephenB
I prob should have mentioned that there could be a max of 4 connections (aka my family) streaming from the NAS (Plex) an any one time, so in that case would it still not make a difference using 'bond' you reckon ?
xlr8r wrote:
I prob should have mentioned that there could be a max of 4 connections (aka my family) streaming from the NAS (Plex) an any one time, so in that case would it still not make a difference using 'bond' you reckon ?
Four simultaneous Plex connections won't create congestion on a gigabit ethernet connection, as even a 100GB 4K BluRay rip has a data rate ceiling of 144 mbps. Most 4K content has a much lower data rate (generally less than 40 mbps). You can use MediaInfoXP to check the bitrates in your media library.
FWIW, I had LACP enabled on my own Pro 6 for a while, but eventually just turned it off. I didn't see any noticeable performance improvement. While there are times when I wish directory searches and small file transfers were faster, the issue there is the iops limitation of my mechanical disks, and not the network.
MultiGig ethernet is a better way to deal with network bottlenecks than LACP (or any bonding mode). but that is not something you can upgrade on the Pro 6.
My own approach to Plex (really all applications) is to run it on a PC with the NAS volume mapped to a drive letter. The PC I am using has an Nvidia GPU, so it is much better at transcoding than any ReadyNAS.
xlr8r wrote:I was hoping to upgrade the ram to 2x4gb 1066 (from 800) just have a little more 'oomph!'...for transcoding etc
The max FSB on the Pro6 is 800, so 1066 RAM will still run at 800.
aw not good, i thought i read somewhere on here that it did support 1066 and that's why some folk upgraded to 1066..?
xlr8r wrote:aw not good, i thought i read somewhere on here that it did support 1066 and that's why some folk upgraded to 1066..?
Definitely limited to 800. Some may use 1066 just because it was easier to find, or some may not realize it won't make a difference. You can gain a very small amount of speed with lower CAS latency memory.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
