Optimizing read transaction startup time: Unicode ate my perf and all I got was

added by DotNetKicks
10/26/2016 12:10:29 PM

2 Kicks, 285 Views

As you can see, over 60% of this function is spent in just converting to lower case, which sucks. Now, we have some additional knowledge about this function. For the vast majority of cases, we know that this function will handle only ASCII characters, and that Unicode document ids are possible, but relatively rare.