Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

We have a strange requirement for Quartz perhaps.

We require a stop-gap solution for a specific problem we are facing in one of our systems came up with an odd solution that would require us to set a high limit on the number of Quartz threads/jobs able to run.

Has anybody ever run with nearly 300 Quartz threads active? How might Quartz run in this situation?

Environment: Two clustered Oracle app servers.

John Eichelsdorfer

Yes, a number of users run with 200 to 500 worker threads.

How this behaves depends a lot on the nature of your jobs. If they are short-lived jobs (i.e. their execution only takes a second), then such a number of threads will cause serious lock contention in the Quartz internals (locks around the integrity of the job/trigger data). But if the jobs take a while to run, and particularly if they perform blocking operations (e.g. network i/o) then you are likely to benefit from a large number of threads.

Experimentation with your particular setup and jobs will probably be key to finding the "sweet spot".

Thanks, James. We may need to give you a call again on this at some point after the holidays.

John @ ert