Mitch's Blog

Users often want a bullet-proof solution for application performance, however, in reality, performance is more art than a science due to the methods necessary to diagnose & improve.

DNN Platform is amazing, however, if you expose public registration you can often get bombarded by spam user registrations which can take away from your day. This post explores options to limit those registrations.

Module developers have many choices as they create their extensions. One of which is around the level of emphasis placed on performance, a few simple things can set your module apart from others with these performance tweaks.

You can have the fastest application server in the world, but if your application does not handle client-side interactions well your performance will still suffer. This post explores client-side optimizations for performance.

With the prior post getting metrics in place, now we shift focus to understanding the users and environment and how they can impact our performance.

Improving web application performance can be a monumental task, this is the first post in a series geared towards removing some of the complexity. Metrics are key for validation of performance changes, and a good starting point.

DNN provides two different caching mechanisms that can be configured to improve performance; ModuleCache and PageOutputCache. Proper configuration and use of these can make drastic improvements to performance.

DNN's ability to support multiple portals is an amazing bit of flexibility, however, if not properly configured major performance issues can arise that are hard to diagnose.

DNN's functionality to display a module on all pages might seem like a good idea, however, it can be a true nightmare. This workaround is much nicer.