I have found that if a server has several Infobases and every infobase has some scheduled job which runs, for example, ones a minute, it will consume almost all CPU resources and a lot of disk resources probably if not cashed.
It appears that if no user is logged, scheduled job will start complete session, which could take up 10 seconds with high CPU usage. If there are, for example, 10 similar infobases (a group of companies) it tries to run 10 new sessions every minute which consumes all the CPU cores.
What should we do? The job is actually runs at a fraction of a second. We can not merge infobases. We can not buy 10 servers (and do not want to). We need some regular checking of information updates.
1. Could the scheduled job be executed only if there is active user session?
2. Could I use external trigger (web service for example), so only if condition is met scheduled job will run?
3. Is there any way to keep context in memory so not to prepare it for every single job run?
This forum is intended for cases when a problem can not be solved due to restrictions of the platform: a bug or lack of functionality.