Load-test of Async: Slow or Errors
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
I wrote a question on StackOverflow about horrible performance with Dapper being used asynchronously. Originally I thought the problem had little relationship to Dapper. But the more I tested, the more the results pointed to Dapper.
I've revised the StackOverflow question accordingly - but this is why the question is posted on SO instead of here. Now that I think it is a Dapper problem, I'm making this issue point to the SO post.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Stack Overflow question and its load-test details, then inspect Dapper's asynchronous data-access path. Done would require reproducing the reported slowness or errors and establishing a verified correction or explanation in Dapper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100