Jobstream - negative Performance Impact - post upgrade to the September release

Hi ​@Haydn 

We haven’t noticed any major slowdowns in job stream execution overall but we did observe a noticeable spike in October.
 

I

We also saw a slight increase in the number of failed jobs during October along with some new error messages that we hadn’t encountered before.
 

The request failed with HTTP status 503: Server Too Busy.

I’m not sure if this helps or proves anything but I wanted to share the results with you since the timing of the spike is interesting.

Best, 

Michal 

Hi Michal, thanks for your feedback, I really like your overall tracking of success vs failures, I think I might include that in my report too 😀

​@Haydn - I believe it depends on what job streams you are running.  We saw an increase in run times for updating our tabular models and Planview acknowledged a change to the structure table that could impact processing times. They were able to find a resolution that reduced our run times back to what we were seeing previously. You can ask them if your slowness could be similar to NASCO’s reported issue in case 952819. 

Best regards,

Pam Sargent
NASCO