Hi,
in the documentation for JOB_QUEUE_PROCESSES, it says that range is 0 - 1000, but I am interested in some optimal value.
Is it a bad idea to have a database where lot of business actions are performed in the background, asynchronously, over jobs. Where jobs are fired very often, sometimes more then one in the same second and where it could happen that lot of them runs in parallel for some time ( maybe 100 ). Some of the jobs are small, couple of seconds, while some of then could take hours to complete. Also, some of the jobs would run in their scheduled time, while some would be explicitly fired with JOB_RUN(...) statement ( current_session = FALSE ).
Please tell me do you see such architecture as a problem, from performance or any other point of view ?
thx