xxjingcd opened a new issue, #13472: URL: https://github.com/apache/dolphinscheduler/issues/13472
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened The Quartz Scheduler of Api doesn't need to start, and the threadpool will be idle. But the `org.quartz.simpl.SimpleThreadPool` will create all threads in it's `initialize()` method，which will causes performance overhead; ### What you expected to happen The Quartz Scheduler of Api use `org.quartz.simpl.ZeroSizeThreadPool` which has zero Threads; More description about [ZeroSizeThreadPool](https://www.quartz-scheduler.org/api/2.1.7/org/quartz/simpl/ZeroSizeThreadPool.html)： >The pool has zero Threads and does not grow or shrink based on demand. Which means it is obviously not useful for most scenarios. When it may be useful is to prevent creating any worker threads at all - which may be desirable for the sole purpose of preserving system resources in the case where the scheduler instance only exists in order to schedule jobs, but which will never execute jobs (e.g. will never have start() called on it). ### How to reproduce Jconsole monitor ### Anything else _No response_ ### Version dev ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
