Junwei Lian

> Conductor in its current form is not built with real-time scenarios. However, in this case, i would check your connectivity from Conductor -> Postgres and see if there are...

@aravindanr yes. After the cluster mode (3 nodes) is deployed, this problem does not occur. Only when the qps is high (qps=50), the CPU utilization rate is high.

The following is my configuration： `spring.application.name=conductor springdoc.api-docs.path=/api-docs conductor.db.type=redis_standalone conductor.redis.hosts=10.00.00.00:3380:us-east-1c:666666 conductor.redis.dataCenterRegion=us-east-1 conductor.redis.availabilityZone=us-east-1c conductor.redis.maxConnectionsPerHost=1000 conductor.redis.taskDefCacheRefreshInterval = 1 #conductor.redis.eventExecutionPersistenceTTL conductor.redis.workflowNamespacePrefix=conductor-stable conductor.redis.queueNamespacePrefix=conductor-queue-stable conductor.redis.queuesNonQuorumPort=22122 queues.dynomite.threads=20 conductor.indexing.enabled=true conductor.elasticsearch.url=10.00.00.00:9260 conductor.elasticsearch.indexName=conductor-stable conductor.elasticsearch.version=7 conductor.elasticsearch.asyncWorkerQueueSize=100 conductor.elasticsearch.asyncMaxPoolSize=12 conductor.elasticsearch.asyncBufferFlushTimeout=10 conductor.elasticsearch.username=es conductor.elasticsearch.password=tsp1024 conductor.default-event-queue.type=conductor...