You might heard params are evil. Have you ever seen the performance bill for that? How to find out where params are used? Memory allocation report shows all allocations, we’ll start from here: Method with params creates an array behind the scenes, so hunting for object: IL code proves sad truth – array is alwaysContinue reading “Performance crime: Params”
Let’s start with a guess – what is the most CPU-heavy operation in Sitecore? Answer: Performance counters initialization: Yes, that’s right, those performance counters which are powered by OS and super fast. Although Sitecore counter init implementation does not look offensive (volatile read & interlocked), counters are everywhere (cache lookup / access / object creation):Continue reading “Reckless interlocked operations”
Why ‘Sitecore is not testable’ cliche is no longer actual.
The case study on how the harmless collection could silently cause system to work slower and remain undetected for ages.
Would you as a developer allow a setting that can make system 15 550 times slower? I’ve received a few memory dumps with high CPU; each scavenges AccessResultCache: How big is the cache so that every snapshot contains the operation? Detecting cache size from the snapshot A ClrMD code snippet locates objects in Sitecore.Caching.Generics.Cache namespaceContinue reading “Performance crime: config to kill performance”
How expensive a lack of respect to mainstream usage could be?
The amount of memory cache can use is defined in config: That is needed to protect against disk thrashing – running out of physical RAM so that disk is used to power virtual memory (terribly slow). That is a big hazard in Azure WebApps – much less RAM compared to old-school big boxes. Sitecore keepsContinue reading “Performance crime: wrong size detection”
Breeze in life into Sitecore Fast Queries.
Why a powerful mechanism is not applied in modern designs?
How to answer ‘why slow’ question?
Why to visit buildStuff?