Jonny Bekkum

Must be something I'm doing wrong. When I run all tests there is negligible difference whether tests is running with EnableThreadSafetyChecks(false) and not. Closing the issue.

After reviewing the code I found that I had somehow EnableThreadSafetyChecks(false) in both tests. When comparing with original test it is still about 15% faster when ThreadSafetyChecks i disabled. So...

from Julie Lerman : https://www.youtube.com/watch?v=bXZCdoKpjts&t=1850s  See: https://github.com/dotnet/efcore/issues/23611#issuecomment-778191277 and https://github.com/dotnet/efcore/pull/24125 And from the summary in EF Core Advanced Performance Topic: ### Reducing runtime overhead However, for high-performance, low-latency applications where...

Merged in PR #64

Merged in PR #63

I'm wondering about the disposal of _currentResultSet i BufferedDataReader. The memory dump show that the memory is referenced in _currentResultSet and this is not disposed/cleared when BufferedDataReader is Closed /...

Yes, that will work for PooledDbContext but if you have a long living DbContext the _currentResultSet variable will not be cleared until the next query is executed. Maybe no problem.

No, my mistake from not being so familiar with the internals of EF Core.

First of all - I have verified that the fix in main is good for EF Core 7. I have tried to create private build from main (release/7.0) and it...

I verified the fix from the daily build feed but tried to test changes in Clear method in StateManager by creating a private build and that failed on assembly load...