Pulse memory leak

Hi, for the first time our Deadline Server crashed today. When we logged on the server there where low memory messages(both ram and swap). The computer was still running but it was impossible to do anything, even reboot from the start menu. We had to close and re-open the machine.



I think there might be a memory leak in Pulse. I would have liked to send some logs, but the computer was so jammed that it was impossible to take snapshots or anything.



There is a total of 500 jobs in the repository, roughly 60% of them completed.



I have found the with Pulse running the refresh where a lot faster but all the job edits where slower. Example right clicking on a job to acces the logs or errors is slower with Pulse running.

Thanks for the feedback. We have found that pulse sometimes has trouble handling large amounts of jobs in the queue, but not so bad where it crashed the machine. We will continue to try and tweak pulse so that Deadline speed is optimal, so information like this is extremely helpful.



If you find that pulse is causing you problems, simply close it and Deadline will continue to run as normal without Pulse.



Cheers,

  • Ryan

I am trying without pulse for a few days to see the difference.



That’s what I like about this software. Hopefully you will be able to twaek it to perfection.



Sylvain Berger | Technical Director | Alpha Vision


One more thing, we noticed that without pulse, when all computer are rendering the CPU of the server are fairly low (around 30%)



With pulse running, when all the computers are rendering, the server cpu are running a lot highier (around 80%)



We will try to output the cpu and ram values for a full 24hour period with and without pulse. I will send you this information as soon as I have it.



Sylvain Berger | Technical Director | Alpha Vision