DBMS_SCHEDULER is slow for multiple jobs who has the same Start_date
The database version 11.1.0.7
Operating System Microsoft Windows x64 (64-bit)
We are using the DBMS_SCHEDULER jobs for timed Objects inside a workflow. So this could result in 1000 or more Object who has the same expiration_date (start_date) but the scheduler only runs about 10 to 20 Jobs at the same time and this only every about 2 second.
Is there a way to improve the scheduler so he can run all 1000 Jobs at once or that the repeat_interval of these about 2 seconds is better?
In our case the scheduler runs ~12 Jobs at the same time who makes an update on a table or an insert and after that he waits 2 seconds until he runs the next ~12 Jobs...
Operating System Microsoft Windows x64 (64-bit)
We are using the DBMS_SCHEDULER jobs for timed Objects inside a workflow. So this could result in 1000 or more Object who has the same expiration_date (start_date) but the scheduler only runs about 10 to 20 Jobs at the same time and this only every about 2 second.
Is there a way to improve the scheduler so he can run all 1000 Jobs at once or that the repeat_interval of these about 2 seconds is better?
In our case the scheduler runs ~12 Jobs at the same time who makes an update on a table or an insert and after that he waits 2 seconds until he runs the next ~12 Jobs...
0