Why Does SharePoint Start-up So Slowly?

A question that comes up often is why SharePoint takes so long to do anything the first time something’s accessed after an IIS restart, or machine reboot. Typically for a non-technical person this is what triggers this question: A page is opened in the browser by the user. SharePoint takes its’ sweet time getting said…

2

Getting SharePoint Event IDs “90hv” and “nask” Despite Disposing Just Fine

Most SharePoint developers will have probably have seen these SharePoint event IDs at some point or other, especially if you’ve ever worked with server-side code before. How to properly manage server-side SharePoint objects is pretty well documented already, but I’ve found it’s still easy to reproduce these “errors” even with good clean-up logic in code. I’ve seen…

0

SharePoint Performance Monitoring with Azure

Aside from epic scaling possibilities, another cool ability Azure gives us is HTTP endpoint monitoring – the ability to check our SharePoint apps are responding nicely, even from various locations around the world if we want it. This is fairly quick article mainly thanks to the brilliant simplicity of how this works. Add Endpoint Monitoring…

1

AlwaysOn Asynchronous vs Synchronous Commit Performance for SharePoint

Hot on the heels of the last analysis showing the performance hit for a synchronous SQL Server AlwaysOn cluster, re-running the same tests show a distinct performance boost when asynchronous commits are used. In fact it’s nearly the same as standalone at that point, which makes sense as DB updates aren’t restricted to needing confirmation…

1

SharePoint & SQL Server AlwaysOn vs Standalone Performance

How to setup SharePoint with SQL Server AlwaysOn has been covered nicely now, but I’ve not covered the performance hit setting up such a system will incur. The short version is: updates are about x2 slower than standalone for a x2 node AlwaysOn cluster; reading data is about the same performance (which would make sense)….

8

Reduce AppFabric Calls to Active Directory for SharePoint Farms

AppFabric is a key part of any SharePoint 2013 as we all know by now. It’s used for many things indeed all over the product and AppFabric in turn uses Active Directory to make sure only authorised processes get access to the cache data. Thus when SharePoint uses AppFabric, it opens a new TCP connection…

0

Troubleshooting AppFabric Timeouts on SharePoint

SharePoint 2013 uses AppFabric to host a bunch of stuff in a cache-cluster. This is awesome mainly because each web-front-end server doesn’t have its’ own cache island that can’t be shared with the other web-front-ends and the likelihood of a cache-miss is much lower (especially if the load-balancer doesn’t do sticky-sessions), thus the caching becomes…

4

The “High-Availability SharePoint” Bible

A big interest of mine is designing SharePoint farms to be highly-available through good architecture & solid design; something I’ve posted about quite a bit on this blog over time. This article summarises the high-availability strategies available for SharePoint and then touches on other common areas that cause SharePoint farms to fail, as a sort…

0

Changing Indexer Performance Setting in SharePoint 2010/2013

Just a quick note for anyone that used MOSS/SharePoint 2007 and is wondered why the option to change the indexer performance has been removed in SharePoint 2010/2013. Well worry not SharePointer, it is still there. Where is it in SharePoint 2010/2013? It’s just moved to PowerShell – Set-SPEnterpriseSearchService to set it and Get-SPEnterpriseSearchService to see…

2