Vray Proxies bring our sever to a crawl.

[Dave_Wortley]

Does anyone else have this problem when using VrayProxies.

If we are using them on large scenes (big print resolution) and we VrayProxy a few big meshs we find that the constant loading of vrayproxies causes our server to be overloaded.

1024 render buckets each loading Vrayproxies is a lot of reading from our RAID.

I've written scripts that copy the vrmesh files locally to the machines and repaths which cuts off a fair bit of the overhead but still the render doesn't render as quickly as it should do with loading of the files constantly.

Vlado, is there any guidlance for how vrayproxy meshes should be used to maximise performance?

Is there any way you could make Vray have an option to copy all the vrmesh files locally to the machine first and then remove them at the end of the render so they would have better reading speeds?

[ruebenad]

Dave did you find any information to solve this issue?

[flino2004]

To me the best way to go is having a copy of your assets locally ( textures and proxies)....so one person is the manager of the assets, so everybody knows what you have.
if I have a special texture or a version of an existing texture map for a project I create a folder inside my project main folder named MAPS.
I use Refamo, it has a feature to copy files to all the render nodes in one shot, you can pretty easy update all the local asset drives.

Fernando