So I’m wondering of what the best practice is for the location of the Deadline Repository on a server:
— the server C drive
— the server main storage area
Seeing as how the repository is read/write quite a bit, I’m curious to hear what the Deadline core team thinks. I’ve looked over the documentation and around the web, but haven’t been able to find a suggestion.
Amazing piece of software. Been using it for years. Thanks!
Hi Jason,
This section of our docs including the last paragraph really sums up our repository requirements:
docs.thinkboxsoftware.com/produc … repository
That being said, we have an old Deadline v5 scaling whitepaper here:
thinkboxsoftware.com/deadlin … caling.pdf
However, it should be noted with the MongoDB in place now, the main consideration is if your submitting your ‘data’ (scene) files into the repository or referencing them off your fast dedicated storage, you might already have in place.
Using SSD’s is highly recommended for any storage solution you are considering as they are both fast and quite cheap these days. Typically, a Windows file server’s “c” drive is just for the operating system and then it has some dedicated drives to be used for storage, which is where you would place the repository. The great thing with the repository is its easy to scale as and when and if, your farm increases in size, using standard IT practices for common file storage & serving. So, first question that most users should ask, is how large is your farm now and how big will it become in the future in your business. Based on that answer, IT practitioners can start to put together a business plan on what should be used.
I think at some point, we should update our whitepaper, to provide some example setups for different size studios.
Please do ask more questions and I’ll try to best advise. However, this stuff tends to all be quite studio specific.