danielgerlag / danielgerlag/workflow-core
Load test throws Connection errors with MongoDB
- Dominant language
- C#
- Stars
- 5.9k
- Forks
- 1.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
**Describe the bug**
I tried to load test workflow core with a simple hello world program with 5000 requests and 5 pods.
**To Reproduce**
load test workflow core with a simple hello world program with 5000 requests and 5 pods. Used RabbitMQ, Redis, MongoDB
**Expected behavior**
Should not have thrown errors (It was 20% errors and throughput went from 200/sec to 13/sec after 1300 requests.
**Additional context**
Error: Thread pool starvation
What I Tried: I created a singleton class of MongoDBClient and sent it as a param in UseMongoDB().
Am I missing something here? It seems to be working great initially but stops with thread starvation error.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the workflow-core load test with a hello-world workflow, 5 pods, 5000 requests, RabbitMQ, Redis, and MongoDB. Start by examining the MongoDBClient singleton passed to UseMongoDB() and the reported thread pool starvation; done means the connection errors and starvation no longer occur under this load and throughput does not collapse.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, mongodb, rabbitmq, redis
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100