When a subscription is triggered, hundreds, or thousands of jobs can be created.
Currently, there is no way to limit the ressources that these jobs will use, so they end up using all the ressources of the IS, making it harder for users to access the service.
It would be nice to have the possibility to limit the amount of ressources used by sheduled jobs (for example 20% of the CPU), or set their priority to low, so that they could 'run in background', without putting the IS on its knees, and without interfering with regular users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.