Have you ever noticed that your SharePoint site just gets slower and slower? That’s probably because the performance of Structural Navigation is absolutely horrible, especially vs. Managed Navigation. This blog post includes our findings about the issue, and I also include some explanation of the reasons behind the difference and a simple comparison to Search-based navigation.
- By far the most customizable and tweakable option
- Easy to edit for editors/admins
- Good performance on-premises, as long as WFEs are powerful, site structure isn’t changed periodically, caching is used and master page hasn’t been modified to include riculous amount of levels
- Abysmal performance on O365, if there are over 10 items in the navigation
- Security trimming is automatic
- Security trimming not available
- Exception: For SP2013 it’s available for term-driven page links
- Editing experience is more confusing, but at least it’s using the standard termset editor
- Not updated automatically (unless you’re using solution like Valo)
- on-premises: good
- O365: fine (beats structural anytime there’s over 10 links)
- (Kind of) the recommended solution by Microsoft
- Performance is good both on-premises and O365
- Security trimming available
- Confusing editor experience
- Bad customizability
Performance difference (measured in SPRequestDuration) between structural navigation and managed navigation
|Test number||Dozens of sites||Inheritance cut, limited amount of sites||Full-blown navigation|
(Numbers are from a customer’s production environment – thanks for the anonymous contributor!)
So, why is Structural Navigation so slow on SharePoint Online?
The difference comes from Structural Navigation being awfully slow in SharePoint Online. That might strike some readers as weird, since its performance in on-premises environments is typically decent.
The issue is caused by the in-memory navigation node cache solution Structural Navigation is based on. This cache is located on WFE servers – and in an on-premises environment, you typically have only a few servers that you might land on. With any luck, those servers already have your navigation nodes cached, as you’ve probably visited them before. In SharePoint Online there are thousands of WFE servers that serve any given tenant, and you might end up on any of them. That means, that the server probably doesn’t have your navigation nodes cached, and it’ll have to rebuild the cache for each request. Understandably, this causes huge load times.
Sources and references
- This data is from Valo deployments. www.valointranet.com
Latest posts by Antti K. Koskela (see all)
- 4 ways to fix error AADSTS65001 (The user or administrator has not consented to use the application) - November 20, 2017
- How to use the Azure AD associated with your SharePoint Online - November 3, 2017
- New version of Microsoft.IdentityModel.Clients.ActiveDirectory (ADAL.NET) is out – good time to update! - October 27, 2017