Why you should care about what you return in your ScheduledJob.Execute
Why You Should Care About What You Return in Your ScheduledJob.Execute
Welcome back to my blog
Finally get my blog up and running again, welcome
Fatal Flaw with Geta-NotFoundHandler
A deep dive into a fatal flaw in Geta-NotFoundHandler that caused high CPU usage due to an endless loop triggered by an empty redirect rule.
Solving the Mystery of High Memory Usage
Solving the Mystery of High Memory Usage
A Curious Case of Free Objects
A memory dump investigation into rising memory usage and the mystery of free objects in the Large Object Heap.
Loading sos.dll to Windbg for .NET Core: The Correct Way
Loading sos.dll to Windbg
AsyncHelper Can Be Considered Harmful
AsyncHelper Can Be Considered Harmful
The Search for the Dictionary Key
The Search for the Dictionary Key
Fix your Search & Navigation (Find) indexing job, please
A deep dive into a performance issue caused by nvarchar(max) misuse in a scheduled indexing job.
Varchar can be harmful to your performance
As string is the most common data type in an application, nvarchar
and its variant varchar
are probably the most common column types in your database. (We almost always use nvarchar
because nchar
is meant for fixed length columns which we don’t have). The difference is that nvarchar
has encoding of UTF-16/USC-2 while varchar
has UTF-8.