Should the server be unrepsonsive, please notify me by clicking the button below. If you wish to leave a note, you may do so but it is optional. Note it is public, so don't post any sensitive information!
If it's a regular issue, and just needs a reboot don't worry about explaining. Just click Report and then kick back and wait please. If issues are reported between 21.00 and 6.00 it will most likely be resolved as soon as I'm awake and checking my email, so please be patient during out of office hours.
If you look below and see an issue reported but is waiting on an action, please feel free to either just wait for me to reboot it, or hit report again to add another notification.
Anything else please feel free to email me directly.
All times are in GMT
The server has seen an uptick in use over the last few weeks, and I think we need to start being a bit more mindful on setting up render settings and use in general.
The Iray server software is a fickle beast and it's easy to get into a situation where the server is loaded up with 20+ jobs, the cache file hits 100gb+ and it just grinds to a halt with no other option than to delete the cache (and subsequent jobs) and start over.
I'm hyper aware that this can cause annoyance - so before people start cancelling out of frustration, I'd like to see what we can do collectively to try and smooth these bumps out.
There are a number of users who submit jobs and either remove or set impossibly high render settings.
For those unaware, Iray uses these settings to determine when to stop rendering. Either it meets the number of iterations, time limit or quality.. or whatever those that are set.
So if you have an large image, which is set to 15000 iterations, no time limit, or no quality, that image will render until that iteration limit is met, regardless if it is 20 mins or 20 hours. Obviously, this is an easy way to bog the server down, particularly if busy.
This also causes a potential problem if the job drops from the GPU to CPU rendering - that means it's going to be glacial trying to render that and essentially it's just locked the server up until either I know, or am alerted. This then creates a backlog, and then the cache issue comes into play as well.
So please can I suggest we look to be more efficient with these. I appreciate some shots will need more samples, but huge renders with quality and time settings disabled are a little overkill. Ideally I'd like to see everyone set a time limit of an hour (so 3600 seconds) a quality of 1 and 15000 iterations. If these settings produce noisy renders, then adjust, but pay attention to the results - if the render stopped after 20 mins as it hit the iteration limit, then just increase that. Don't just max everything out please.
Also please consider your render resolution - a lot are now being rendered 3000+ pixels, which is ok if you keep the other settings manageable. I do it myself, and then resample down, but now it just seems everything is getting set to max, huge scenes, huge resolutions.. and it's impacting everyone else.
Hopefully keeping the server moving a bit more will mean I can reboot and clear the cache when its quiet as well.
Please be mindful of others - some people use it more than others, so if you see 1 job behind your 5+ please consider just setting your priority to 101+ to let others go first (but again, bear in mind if you load up a lot of renders, they could be culled in a cache clear out)
|Current Date Time||Note|
|Log Date Time||Note|
|2021-02-28 19:51:47||9090 down for about 45 mins.. same reason..nearly done!|