Daniel Ovaska
Mar 5, 2019
  5393
(2 votes)

Performance - GetChildren vs GetBySegment

GetChildren is a decent method that is also cached in the background. But if you have 1000s of children you will get some performance hits. Another good option if you are only searching for a single content item is to use GetBySegment method. This one works well with large amounts of children with excellent performance. 

I tried it on folder that has 13000+ children (yes, bad idea) and these were the results when running on local machine

  1. GetChildren
    
    foreach (var folder in ContentRepository.GetChildren<ContentFolder>(parent)​)
    {
       if (folder.Name == customerId)
       {
          ...                    
       }
    }
    17.857s
  2. GetBySegment
     var customerFolder = ContentRepository.GetBySegment(parent, customerId, LanguageSelector.AutoDetect());​
    0.147s

So that's a pretty huge performance gain by more than a factor 100. Hope it helps someone out there to pick the right tool for the job. 

Few children => GetChildren
Many children => GetBySegment or Episerver Find...

Happy coding everyone!

Mar 05, 2019

Comments

K Khan
K Khan Mar 5, 2019 02:29 PM

Thanks for sharing, any suggestion for contentRepository.GetAncestors?

Praful Jangid
Praful Jangid Mar 5, 2019 03:07 PM

So, is this GetBySegment(...) works as a filter by ContentId you passed on (second parameter)?

But, if I see the definition here, that is accepting urlSegment as second parameter. What is that? Or do we have overloaded functions for this?

Daniel Ovaska
Daniel Ovaska Mar 5, 2019 03:17 PM

K Khan: Don't think that method will be a problem. Unless you have very very deep tree structure. Have you seen any performance issues with that one?

Praful Jangid: It's a filter but on the url segment yes. Url segment is the part of the url for that page that is visible in browser. For instance, the url segment for this blog post is performance---getchildren as you can see above in the browser. So if you know the url segment (or route segment as it's also called) you can use that to fetch the page.

Daniel Ovaska
Daniel Ovaska Mar 5, 2019 03:22 PM

So for instance, if I'm building this blog on Episerver world and I want get the 2019 folder for blogs and I have this structure

https://world.episerver.com/blogs/Daniel-Ovaska/Dates/2019/3/performance---getchildren/

If I have the parent page with url 

https://world.episerver.com/blogs/Daniel-Ovaska/Dates/

I can then use contentRepo.GetBySegment(parent,"2019",LanguageManager.AutoDetect()) to get the page with url

https://world.episerver.com/blogs/Daniel-Ovaska/Dates/2019/

Erik Norberg
Erik Norberg Mar 6, 2019 01:37 PM

If you are going to use GetBysegment you have to use caution.

I recently filed a bug about it that has been deemed "by design". If GetBySegment doesn't get a match in the provided language it will return a match for any other language it can find. It might not always be the expected or desired behaviour.

Daniel Ovaska
Daniel Ovaska Mar 14, 2019 08:52 AM

Good to know! 

Please login to comment.
Latest blogs
Optimizely CMS 13: What Actually Changed and Why It Matters

I had the privilege of attending a deep-dive session on CMS 13 this week, and after seeing the full roadmap laid out across these slides, I wanted ...

Aniket | May 12, 2026

Introducing the Optimizely MCP Server: AI That Speaks Commerce

MCP AI Commerce B2B Claude ChatGPT OpenAI Optimizely Insite Commerce Introducing the Optimizely MCP Server : AI That Speaks Commerce We've connecte...

Vaibhav | May 12, 2026

AEO, GEO and SEO with Epicweb AI Assistant in Optimizely CMS

Traditional SEO remains important, but content must now also be optimized for answer engines and generative AI. This article explains how the Epicw...

Luc Gosso (MVP) | May 11, 2026 |

Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 1 of 2)

How Niteco's Upgrade Machine   uses orchestrated AI coding agents to deliver a buildable baseline and a running CMS, then hands over for...

Hung Le Hoang | May 11, 2026

Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026