Black Friday is coming, and we are working hard to make sure customers running on Optimizely DXP that anticipating a Black Friday campaign, will be in good shape when the traffic hits. As they say - the optimization season is in full swing. This time, let’s take a case study of how we can identify and optimize a (very) expensive query.

There are things in life that excites and scares you at the same time. Recently I helped out a case when it’s both exciting and scary. The problem was a gigantic 106 GB memory dump with a very small managed heap compared to the dump’s size. That hints unmanaged memory leak. While I’m fairly confident with memory dump analysis, I haven’t had a lot of good luck with unmanaged memory leaks. It could have turned into a big headache and unknown territory. But if it’s not me then who will go to hell? Then game is on.

Why You Should Care About What You Return in Your ScheduledJob.Execute

Finally get my blog up and running again, welcome

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

A memory dump investigation into rising memory usage and the mystery of free objects in the Large Object Heap.

Loading sos.dll to Windbg

AsyncHelper Can Be Considered Harmful

The Search for the Dictionary Key