HangfireIO / HangfireIO/Hangfire

Hangfire.Redis performance issue

Open
#1,229 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
10.1k
Forks
1.8k
Avg merge
1h 19m
Merged PRs (30d)
1

Description

Hi all,

We used to have a Hangfire & MSSQL pairs. After having performance issues, we bought Hangfire.Pro to be able to use Hangfire on Redis. Now, we have a Hangfire server runing on Redis. But performance problems still go on. Under stress (100 concurrent user), Hangfire (client) deletes a job approximately 1 second (normally, avarage of the delete operations' time is 50-60ms). I think, Hangfire and Redis should've been faster.

Maybe I'm missing a point. How can I diagnose the problem or speed Hangfire operations up?

Edit: By the way, I know, it depends on what your Redis server is. Our Redis server is Azure Redis (PaaS) [Standard C2](https://azure.microsoft.com/en-us/pricing/details/cache/). It's not that much bad :) It can handle 100 concurrent request.

Hangfire.Core 1.6.19
Hangfire.Pro.Redis 2.2.1

Contributor guide

Open the contributing guide

Research direction

The issue names Hangfire.Core 1.6.19 and Hangfire.Pro.Redis 2.2.1 but no files or tests. Start by reproducing the reported delete latency under roughly 100 concurrent requests against the stated Azure Redis Standard C2 setup, then profile the client and Redis operations. Done means identifying a reproducible bottleneck or configuration cause and documenting a supported corrective action.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, redis
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.