Closed WebApelsin closed 7 years ago
Each instance of the RedisConnection creates a subscription to the redis JobFetchChannel which doesn't released within the object disposal. This leads to CPU usage spikes when the new job arrives and also prevents GC to release memory resources.
RedisConnection
JobFetchChannel
I think the issue can be closed in respect with the merged fix.
Each instance of the
RedisConnection
creates a subscription to the redisJobFetchChannel
which doesn't released within the object disposal. This leads to CPU usage spikes when the new job arrives and also prevents GC to release memory resources.