• State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 3826 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ADSAccount Update Process Task Max Instance

fmoideen
over 7 years ago

Hi,

 

We're running into an issue where we have 5000+ pending ADSAccount Update jobs and each job is taking an average of 18 secs to complete. This would mean about 33 hours for all the jobs to get processed which is unacceptable.

We were thinking of changing the ADSAccount Update process task's MaxInstance to 0 (i.e, unlimited). Are there any adverse effects on doing this? Could this cause updates on the same account to step on each other's toes?

 

Thanks in advance,

Febin

Parents
  • 0 over 7 years ago

    There default setting for the VI.Projector.JobComponent.ProjectorComponent MaxInstance is 0 that is responsible of running the ADSAccount Update jobs. Changing back to the default MaxInstance doesn't have any adverse effects. The calculation of 33 hours is based on that there would be only one slot. With for example 20 slots the it would take only 5 minutes.

Reply
  • 0 over 7 years ago

    There default setting for the VI.Projector.JobComponent.ProjectorComponent MaxInstance is 0 that is responsible of running the ADSAccount Update jobs. Changing back to the default MaxInstance doesn't have any adverse effects. The calculation of 33 hours is based on that there would be only one slot. With for example 20 slots the it would take only 5 minutes.

Children
No Data