Sergei Pavlov
Sergei Pavlov
Also: * Upgrade `Mono.Cecil` & `Microsoft.Data.SqlClient`
Use standard (since .NET4) `System.AggregateException` instead
This property is useful for multi-command transactions. Each `DbCommand.CommandTimeout` property is assigned to remaining time until `Transaction.Timestamp + Timeout` deadline. Also: * Refactor `Transaction` class
Using Virtual-function dispatching minimizes number of branches, which is a bottleneck in CPU This approach applied to `SELECT` translator only as an example. Can be propagated to other frequently used...
Assembly code generated by JIT for Entity.Field getter: before optimization (without `.tail`): ``` push rbp sub rsp,20h lea rbp,[rsp+20h] mov qword ptr [rbp+10h],rcx mov r8,1914C813828h mov r8,qword ptr [r8] mov...
Also: * `recieved` -> `received` * `succesfully` -> `successfully`
The [Field] properties inside class are sorted in order of MetadataToken value. Properties, inherited from base class are first.
In typical ASP.NET apps `.ConfigureAwait(false)` creates unnecessary overhead (a few nanoseconds). `.ConfigureAwait(false)` makes sense mostly for UI applications, with non-null Synchronization Context This can be switched off by setting environment...
We see in tracing this is a hotspot