Wondering if anyone uses a NAS as an Assets drive (where texture maps etc are held)? Wondered how capable they are when performing distributed rendering using 10-20 PCs oin the render? I don’t have much experience with them - I have an old Intel-based NAS at home but it is very slow indeed.
I guess something like a Synology DS414 would be better, but are they good enough to be hammered by a DR without keeling over?
Dual core ..
* 1 gig ram or more
Dual 10 giga ethernet, or dual giga (for both to be full duplex and to work as TEEN)
Internal Connection: SATA III and SSD support.
Try to avoid Qnap are not very reliable.
We use a DS414 for all project folders and resources
Had no trouble at all, been pretty impressed actually. We have 20 pcs accessing simultaneously during rendering.
So much better than having an old windows server box sat there just as a file server imo, depends on your needs I guess.
Interesting. Have you got any kind of ‘special’ switch to handle all the connections and manage prioritisations?
Photoshop files are easily 1GB these days, so if we had a couple of guys opening/saving large files like that, in addition to another couple of guys sending DR jobs for 10 machines to pickup, you reckon the DS414 would cope?
It might be worth looking into using 2 separate NAS boxes - one for reading/pulling assets off for rendering and one for reading/writing scene files and PSDs etc.
Well all I can say is that we have never had any trouble. We have a 24 port netgear switch, nothing special. The DS414 can use 2 ports at once, link bonding or whatever.
Worth mentioning that our max files are 300mb upwards, but we generally dont have such large PSDs - up to 500mb generally.
I donno, I use qnap though its a pro series. I have 16 xeons which can read at once 16 4 GB phoenix cache frames so thats quite a bit of data all on 1gb network and no problems!
Another question on these things:- at the moment, we are using a Windows Server that hosts the domain and it has a number of shares set up so when users log in, they see various drive ‘letters’ for various things. For example, W:/ is the projects drive and G:/ is the assets drive where all the maps/models etc are stored.
If we were to move over to a Synology NAS, do we create drive letters on the NAS in a similar way, or is it done differently? A typical example would be as follows:-
You can set up your users and shared folders etc. using the onboard OS on the diskstation.
Very easy to set up, depending how sophisticated you need the security etc to be. We just have basic different shared folders that only certain users have permissions for.
You can then either map drive letters in windows or just navigate directly through the network using UNC paths (this is what we do)
Theres some useful walkthroughs on their support site
map the drives using script so its the same on all machines. run the script at windows starts as two stage, first remove mapping then add it again, sometimes drive mapping disconnects, so you need to do that.
Well, if you are IT savy, you can of course build a raid 5, or raid 10 or whatever server which will be exactly like the NAS, probably better, what this will involve though is your time. Nas offers that in a bundle thats all. For me, running a small business where I have to do many things at once, and just don’t have the time to do this my self (or knowledge) nas is a good solution.
I think a simple low-power PC running backburner and license servers etc. connected to a NAS is the way forward. This creates redundancy. If your NAS goes down at least your server is up, and visa versa.
This is something I’m intending to do here soon. I’ve just been running all my license servers etc. off my main workstation since it’s on 24/7 anyway, and I have a manual backup solution between the workstation and some local nodes, plus external drives which come home with me for off-site backups, plus web backups for critical admin files. Quite a nice system but a small NAS box would be handy too.
Richard - let us know how you get on with it - would be interested to see your findings.