I know one way to solve this is to set the renders at a
low run level, probably be starting it from a START /BELOWNORMAL
wrapper, but I have also been thinking of QOS on the interface.
BTW, changing [cpu scheduling] priority probably won't change
anything either if the box is thrashing, because at that point
it's not the render process that's using the cpu, it's the swapper.
When a box is swapping, [most] process scheduling is put on hold
while the box tries to stabilize memory.
If a render process keep's requesting more memory resources,
the kernel has to swap stuff out to make room, and if the
renderer keeps doing this, the box just spends all its time
doing high priority swapping.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|