AWS Thinkbox Discussion Forums

DeadlineCommand.exe Slowness

Hey guys,
We started noticing some slowness with our submissions by a factor of 4 or 5 when using DeadlineCommand.exe. After some testing, I discovered that creating a new Deadline repository and setting up a new database completely solved this issue. I’m not sure if this issue is related to this thread we had: http://forums.thinkboxsoftware.com/viewtopic.php?f=86&t=10767, but I think it is.
Is there anything that you know of that could cause this slowness? The whole deadline repository is only around 5-6 gb, so I feel that lookup wouldn’t be an issue here.
Thanks for the help!

  1. 6.1.0.53841
  2. Windows 7/Windows Server
  3. 3ds Max/Vray
  4. Launch a 3ds Max Render using DeadlineCommand.exe

Do you happen to recall anything that may have happened with regard to the server around the time the slowness appeared? Windows updates, application of a new Deadline beta build, etc.?

Hmmm, I posted the last thread because I feel like the problem may have intensified when I ran the MongoDB cleanup…

Is it just submissions that appear slower, or is it deadlinecommand.exe in general? Could you try running deadlinecommand.exe with the -pools argument and compare the speed between the two databases?

deadlinecommand.exe -pools

Thanks!

  • Ryan

So, I stopped pulse and deleted a lot of the completed jobs, and it looks like a day later, everything’s running smoothly, and there’s no difference between the two databases when I run that command…what could possibly have changed?

That’s really strange. I’m not sure what would cause this.

If the slowness does come back in the future, let us know and we’ll try to investigate further.

Cheers,
Ryan

Privacy | Site terms | Cookie preferences