Deadline 2.7 slowness

Deadline
1

I recently updated my Deadline from 2.6 to 2.7 and it seems deadline’s response times to task such as refreshing the monitor to submitting a job are exponentially longer. I have started to implement pulse as well hoping for a decrease in i/o traffic could this be the cause?We are submitting jobs for 3ds max 9 and nuke. Is there something I missed in the update that would be causing this?

Update Deadline 2.7 seems to be maxing out the cpu’s on the server we run it from. Is there a work around for this? I have reverted the system back to 2.6 and I am having no problems with the procs being overloaded.

2

Hi Nick,

Pulse should help alleviate some of the i/o traffic on the server, but the fact that Deadline is maxing out the cpu on the server when Pulse isn't running would indicate that there is a problem. It may be possible that a new feature in 2.7 could be running some inefficient code that is hitting the server more than it should. For Deadline 3.0, we will make it a priority to ensure that no more i/o is being performed then necessary.

Cheers,
 - Ryan

3

I really liked some of the new functionality of 2.7 such as the detailed

info on the slaves including the ram and cpu usage and chance that there

will be another release that I can use?







Nick Swartz


4

Hi Nick,



I would suggest trying to use Pulse with Deadline 2.7 to see if that

helps (we use it here and it’s working very well for us). Unfortunately,

it’s unlikely that we will be doing another release before Deadline 3.0,

so this issue won’t be resolved until then.



Cheers,

5

Ok, Is there a setup manual for pulse? I looked on your site but wasn’t

entirely clear on what to do. This is the steps as I see.






  1.   In repository settings setup server for pulse including port<br>

2. Install and run pulse alongside slaves on render machines

Is that all there is to it?



Nick Swartz

Sway Studio

IT Manager

310.844.7000

nswartz@swaystudio.com



From: Frantic_Deadline Listmanager
[mailto:Frantic_Deadline.listmanager@support.franticfilms.com]
Sent: Monday, November 05, 2007 5:20 AM
Subject: Deadline 2.7 slowness



From: "Ryan Russell" (rrussell@franticfilms.com)

Hi Nick,

I would suggest trying to use Pulse with Deadline 2.7 to see if that
helps (we use it here and it's working very well for us). Unfortunately,

it's unlikely that we will be doing another release before Deadline 3.0,

so this issue won't be resolved until then.

Cheers,
- Ryan

--
Ryan Russell
Frantic Films Software
http://www.franticfilms.com/software/
204-949-0070

To reply:Frantic_Deadline.4276@support.franticfilms.com
<mailto:Frantic_Deadline.4276@support.franticfilms.com?subject=Deadline%
202.7%20slowness>
To start a new topic:Frantic_Deadline@support.franticfilms.com
To view discussion:
http://support.franticfilms.com/WB/?boardID=Frantic&action=9&read=987&fi
d=7
To (un)subscribe:Frantic_Deadline.list-request@support.franticfilms.com



6

These links should provide all the information you need, but if you’re

unsure about anything, let us know:

http://www.franticfilms.com/software/support/deadline/pulse.php

http://www.franticfilms.com/software/support/deadline/pulsefaq.php



Note that Pulse should only be running on one machine (preferably the

repository machine).



Cheers,