After some discussion, we decided to introduce an opt-out flag from thread-safety checks. Unlike with logging, there is no way for EF Core to know when the checks are needed, and when they aren’t; and we definitely want to prioritize reliability and easier debugging, so turning the check off by default was out of the question. Once users have tested that their application works well in production and they are confident that no concurrency bugs exist, they can choose to disable this particular protection; for our TechEmpower Fortunes benchmark, doing so yielded a 6.7% throughput improvement.
This is huge.
Desigur, aveai workaround-uri, dar cam toate erau messy si adaugau complexitate:
- DbContext separat pentru fiecare query executat in paralel (la read-uri mai ales)
- Adaugai Dapper - mix-uri de ORM-uri in solutie + not strongly typed
- Daca aveai un background worker, puneai CUD-urile pe el, cleaner dar tot aveai context separat.
Astept sa vad documentatia finala a API-ului. Sper doar nu fie un flag static ce trebuie schimbat inainte si dupa ce iti faci treaba .