Caching files using BLOB cache is a great performance improvement in SharePoint 2010 Web Content Management solutions. Unfortunately it turns out, that if your files are dynamically created, they are not being cached by BLOB cache. So is creating a custom caching solution the only option to have a good performing solution?
It is a common best practice, while working with the SharePoint server API, to always use context objects whenever possible. Because they have been already instantiated by SharePoint itself, reusing context data doesn’t cause additional calls to the database and allows you to create good performing solutions. However, just because you use SPContext.Current in your code, doesn’t mean your solution is built properly.
SharePoint 2010 contains Developer Dashboard which can be invaluable in optimizing custom solutions for performance. By default the Developer Dashboard is visible only to authenticated users, but sometimes you might want to show it to anonymous users as well. Sounds insane? Find out why you would want it and how to do it.
How good is your Internet-facing website built on the SharePoint 2010 platform?