EPiServer and performance

November 30, 2007

I’m currently working on a large (1000+ subsites) EPiServer project and we had some really nasty issues with performance due to a design flaw. Let me just put it like this: If you’re ever thinking about using many dynamic properties on a large site, DON’T! It has been said before, but needs to be repeated.

The situation has allegedly improved quite a bit in EPiServer CMS (5) but in the 4.XX versions, whenever you delete/move/copy a page the cache is emptied and the entire dynamic properties tree has to be reloaded from the database. Which, in our case, took 30 – 60 seconds and no one was able to use the site for that duration.

The solution was to build a plug-in that iterated through the entire site and moved the dynamic properties to pages instead, e.g. start pages. Then we replaced all the calls to dynamic properties with calls to the start pages’ properties, leaving us with only references to the start pages as “dynaprops” (cool word, eh? I made it up myself). Now every time someone deletes a page, the database roundtrip takes 1 second, not 1 minute.

I hope this can prevent anyone from making the same mistake.


2 Responses to “EPiServer and performance”

  1. Cassandra Says:

    Do you know if this is still relevant is Episerver 5 R2?

    We are currently using Dynamic properties but we have a very large site and are worried about performance!


  2. microserf Says:

    I’m sorry, but I never got around to using EPiServer 5, so I don’t have a clue how well it does scale on that platform.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: