Try our conversational search powered by Generative AI!

K Khan
Sep 15, 2015
  4313
(5 votes)

EPiServer Find performance review

EPiServer Find is a product for free text search as well as content retrieval. It offers an intuitive API for indexing and querying objects. It allows to query data using our own domain model as it recognizes the fact that we know best about our data. It offers a better experience to users, shorter development cycles and cost efficiency.

EPiserver Find Search performance and capabilities are proven but how developers are using those can affect the site performance. If developers are writing queries that involves round trips can effect the performance of page.

//Not optimal
foreach (var article in Articles)
{
      var results = SearchClient.Instance.Search<ArticlePage>()
                                                        .For(article).GetResult();
}
//Optimal
results = service.MultiSearch<ArticlePage>()
                            .Search<Article>(x => x.For("Article1").InField(y => y.Title))
                            .Search<Article>(x => x.For("Article2").InField(y => y.Title))
                            .GetResult();

Indexing data to EPiserver find is a time consuming task and needs consideration when implementing. We need to consider batch size and objects also. EPiserver Find indexing like Bulks.

// Not optimal 
List<MyObject> objects = GetObjectsFromSomeWhere();
foreach (var o in objects)
{
    client.Index(o);
}
// Optimal 
List<MyObject> objects = GetObjectsFromSomeWhere();
client.Index(objects);

By doing this, we will significantly reduce the number of calls sent to the Find index, thus increase the general performance and decrease time taken to index. 

While indexing we have to consider object sizes also. If object size are too large we have to reduce the no of items to go in one index pack. There are few other factors that developers must consider while indexing the data are as following

  • Dont Index the unwanted objects e.g. Images/Videos
    ContentIndexer.Instance.Conventions.ForInstancesOf<ImageData>().ShouldIndex(x => false);
  • Implement the BatchSize for indexing so it can be adjusted to improve indexing time.
    // set the ContentBatchSize to confingured value 
    ContentIndexer.Instance.ContentBatchSize = contentBatchSize;
    
    // set the MediaBatchSize to confingured value
    ContentIndexer.Instance.MediaBatchSize = mediaBatchSize;
    

It will be helpful, if you could share performance issue that you have faced and their fixes also in comments. 

Sep 15, 2015

Comments

Henrik Fransas
Henrik Fransas Sep 15, 2015 12:29 PM

Great post!

Also remenber to cache the the result if you are using GetResult (GetContentResult do it automaticly) like this:

var result = client.Search()
    .StaticallyCacheFor(TimeSpan.FromMinutes(5))
    .GetResult();

And also a great way to improve performance is to use projections instead of returning the whole object, if you for example only are interested in title and author name you can do like this to project it into a anonymous type:

var result = client.Search()
    .Select(x => new { 
        x.Title, 
        AuthorName = x.Author.Name })
    .GetResult();

Or like this to project it into a type'ed object:

var result = client.Search()
    .Select(x => new SearchResult { 
        Title = x.Title.AsCropped(50), 
        Author = x.Author.Name})
    .GetResult();

K Khan
K Khan Sep 15, 2015 02:47 PM

great addition :)

Per Magne Skuseth
Per Magne Skuseth Sep 25, 2015 09:14 AM

Thanks for sharing!
Regarding bulk indexing, check out this blog post for a handy snippet

Please login to comment.
Latest blogs
Build a headless blog with Astro and Optimizely SaaS CMS

I’m a big fan of using the right tool for the right job. I’m also a big fan of Astro , for the right use case. Let's explore Astro to see what it's...

Jacob Pretorius | May 28, 2024

Microsoft announces Natural language to SQL

Finally, Microsoft launches "Natural language to SQL," after it has been available for several months in Optimizely CMS!

Tomas Hensrud Gulla | May 23, 2024 | Syndicated blog

Five easy ways to start personalizing your content right now

If you clicked on this article, you already know that getting the right message to the right person at the right time helps drive conversions and...

Kara Andersen | May 23, 2024

ExtendedCms.TinyMceEnhancements – serwer side webp support

Today I will introduce another small feature of TinyMceEnhancements plugin. The functionality is used to automatically detect whether a browser...

Grzegorz Wiecheć | May 22, 2024 | Syndicated blog

Azure AI Language– Detect Healthcare Content in Optimizely CMS

In this blog post, I showcase how the Azure AI Language service's Text Analytics for health feature can be used to detect healthcare content within...

Anil Patel | May 22, 2024 | Syndicated blog

Stott Security Version 2 So Far

In December 2023, I unveiled the initial version of Stott Security version 2. Although I typically announce each version I release on LinkedIn and...

Mark Stott | May 22, 2024