New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Poor performance because of DbCommand.ExecuteReaderAsync() when reading big string #17373

Closed

forestbat opened this issue Aug 22, 2019 · 3 comments

Labels

closed-duplicate customer-reported

forestbat commented Aug 22, 2019

https://www.cnblogs.com/dudu/p/10423126.html
If you don't know Chinese，see these：
https://stackoverflow.com/questions/40496012/poor-performance-when-loading-entity-with-large-string-property-using-entity-fra
https://stackoverflow.com/questions/28543293/entity-framework-async-operation-takes-ten-times-as-long-to-complete/28619983#28619983
This problem has existed from 2015 to now，if use Dapper's CommandBehavior.SequentialAccess，the problem has disappeared.

Further technical details

EF Core version: 2.2.2
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows or Linux
IDE: Visual Studio 2019 16.3

Member

AndriySvyryd commented Aug 22, 2019

This is likely a duplicate of #885

Author

forestbat commented Aug 22, 2019 •

edited

Loading

This is likely a duplicate of #885

Yes it's duplicate，however you are seem to do nothing.

Member

ajcvickers commented Aug 26, 2019

Closing this as duplicate. Discussion can continue on #885.

ajcvickers closed this as completed

ajcvickers added the closed-duplicate label

ajcvickers added the customer-reported label

ajcvickers reopened this

ajcvickers closed this as not planned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment