You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/01/19 08:11:05 UTC

[GitHub] [shardingsphere-elasticjob] lixiongliang opened a new issue #1813: Expansion of tasks, how to solve them, how to optimize system resources and quick start

lixiongliang opened a new issue #1813:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1813


   At present, we have configured 300 tasks in xml, and will continue to increase in the future. I feel that the system startup has become very slow, it takes a long time, and the number of threads started in the process is thousands. After reading the source code, I found that each configuration job, there will be a separate thread to execute, is there a good and simple way to optimize, integrated Spring configuration is as follows
   <job:simple id="xxxxJob" class="xxxxJob"
                    registry-center-ref="regCenter"
                    sharding-total-count="1"
                    cron="0 30 6 * * ?"
                    sharding-item-parameters="0=0"
                    monitor-execution="true"
                    monitor-port="9888"
                    failover="false"
                    description="Timed task"
                    disabled="false"
                    overwrite="true" job-parameter="31,60"/>


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1813: Expansion of tasks, how to solve them, how to optimize system resources and quick start

Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #1813:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1813#issuecomment-762680099


   You may configure the parameter `executor-service-handler` to specify thread count.
   
   Ref: https://shardingsphere.apache.org/elasticjob/legacy/lite-2.x/02-guide/config-manual/


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [shardingsphere-elasticjob] TeslaCN edited a comment on issue #1813: Expansion of tasks, how to solve them, how to optimize system resources and quick start

Posted by GitBox <gi...@apache.org>.
TeslaCN edited a comment on issue #1813:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1813#issuecomment-762680099


   Consider separate your tasks into different clusters.
   You may configure the parameter `executor-service-handler` to specify thread count.
   
   Ref: https://shardingsphere.apache.org/elasticjob/legacy/lite-2.x/02-guide/config-manual/


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [shardingsphere-elasticjob] lixiongliang edited a comment on issue #1813: Expansion of tasks, how to solve them, how to optimize system resources and quick start

Posted by GitBox <gi...@apache.org>.
lixiongliang edited a comment on issue #1813:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1813#issuecomment-763380806


   Our framework package elastic-job-core needs to be upgraded to 2.x. Currently we are 1.1. I feel that the changes are quite big, and there will be classes that cannot be found.
   
   Dividing tasks into different machines is one way to deploy. The current 2.x custom thread pool DefaultExecutorServiceHandler is also configured for a single task, not a thread pool that applies global tasks.
   
   > Consider separate your tasks into different clusters.
   > You may configure the parameter `executor-service-handler` to specify thread count.
   > 
   > Ref: https://shardingsphere.apache.org/elasticjob/legacy/lite-2.x/02-guide/config-manual/
   
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [shardingsphere-elasticjob] lixiongliang commented on issue #1813: Expansion of tasks, how to solve them, how to optimize system resources and quick start

Posted by GitBox <gi...@apache.org>.
lixiongliang commented on issue #1813:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1813#issuecomment-763380806


   Our framework package elastic-job-core needs to be upgraded to 2.x. Currently we are 1.1. I feel that the changes are quite big, and there will be classes that cannot be found.
   
   > Consider separate your tasks into different clusters.
   > You may configure the parameter `executor-service-handler` to specify thread count.
   > 
   > Ref: https://shardingsphere.apache.org/elasticjob/legacy/lite-2.x/02-guide/config-manual/
   
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org