Daniel Ovaska
Mar 5, 2019
(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)
  2. GetBySegment
     var customerFolder = ContentRepository.GetBySegment(parent, customerId, LanguageSelector.AutoDetect());​

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


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


If I have the parent page with url 


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


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
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog