You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
any updates on your experiment? as a much less scientific / high level profiling experiment, I'm profiling my database connection and seeing single digit ms response times but when dotTraceing the app i'm seeing multiple seconds of total code execution around Dapper.SqlMapper+<QueryRowAsync>
Are you saying if I convert things to not be async that it's magically faster?
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.
The text was updated successfully, but these errors were encountered: