Comments on: Performance Tuning and Optimization of EPiServer http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/ Chatter about EPiServer, ASP.NET, CSS and Web Development. Wed, 21 Dec 2011 01:21:54 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-4105 Fredrik Haglund Mon, 01 Nov 2010 14:00:55 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-4105 Ok, glad to hear that it works well for you. Why it solves your performance issue is another question. You will get the same items cached several times in memory, you get the complexity to setup EPiServer's cache invalidation (propagating publish events between the instances), setup ASP.NET State handling and lose performance to serialization instead and finally you will probably have to buy load balancing licenses (not sure about that). So I would not recommend it unless you have a real need. If you have a lot of requests for static content like images investigate if Kernel Mode Caching can help you to improve your performance. One benefit I can see is that when you have more than one worker process running it can scale better to use your other CPU cores but asp.net applications usually scales well so this might be an indication of thread blocking code? Ok, glad to hear that it works well for you.

Why it solves your performance issue is another question.

You will get the same items cached several times in memory, you get the complexity to setup EPiServer’s cache invalidation (propagating publish events between the instances), setup ASP.NET State handling and lose performance to serialization instead and finally you will probably have to buy load balancing licenses (not sure about that). So I would not recommend it unless you have a real need.

If you have a lot of requests for static content like images investigate if Kernel Mode Caching can help you to improve your performance.

One benefit I can see is that when you have more than one worker process running it can scale better to use your other CPU cores but asp.net applications usually scales well so this might be an indication of thread blocking code?

]]> By: Marco ter Horst http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-4101 Marco ter Horst Wed, 27 Oct 2010 17:39:39 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-4101 Just to update those of you who are interested in this topic: We've been running a Web Garden now for almost 2 1/2 months now on our production system and we're very happy with the result and the performance and capacity boost we gained from it without having to buy new resources. This is our setup: 1 virtual server with 4CPU cores and 8GB of memory 1 App Pool for web users configured to use 3 max. worker processes 1 App Pool for CMS users configured to use 1 max. worker process Both pools are configured to recycle @ 950000KB memory usage as we saw that the website becomes instable @ values above this (regardless of Web Garden setup or not. As you can see, with 8GB of RAM, memory is not really the issue in our setup. Just to update those of you who are interested in this topic:
We’ve been running a Web Garden now for almost 2 1/2 months now on our production system and we’re very happy with the result and the performance and capacity boost we gained from it without having to buy new resources.
This is our setup:
1 virtual server with 4CPU cores and 8GB of memory
1 App Pool for web users configured to use 3 max. worker processes
1 App Pool for CMS users configured to use 1 max. worker process
Both pools are configured to recycle @ 950000KB memory usage as we saw that the website becomes instable @ values above this (regardless of Web Garden setup or not.
As you can see, with 8GB of RAM, memory is not really the issue in our setup.

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-4056 Fredrik Haglund Fri, 13 Aug 2010 12:18:50 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-4056 Yes, this is true but there is also the fact that EPiServer caches all page data in memory. If you enable 2 or more instances they will start compeeting about memory. From a performance perspective it is probably better to scale out and use load balancing Yes, this is true but there is also the fact that EPiServer caches all page data in memory.

If you enable 2 or more instances they will start compeeting about memory. From a performance perspective it is probably better to scale out and use load balancing

]]> By: Marco ter Horst http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-4055 Marco ter Horst Fri, 13 Aug 2010 11:29:02 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-4055 Hi Fredrik, in the blog you state: " ... Do not use Web Garden unless you know what you are doing. ..." In fact, it's not quite so difficult to implement a Web Garden with EpiServer. All thanks to Microsoft's own ASP.NET State Service. The main problem with Web Gardens and EpiServer is session state information. E.g. if you log on to the CMS while your request is being handled by IIS worker process (A) and perform an action in the CMS which is handled by IIS worker process (B), you will get prompted to login again. Not really a workable environment. With the ASP.NET State Service it's fairly simple to handle session information outside of the IIS worker processes. It only requires the service to be started (it ships with Windows Server out of the box) and the web.config to be altered to use it (See: http://technet.microsoft.com/nl-nl/library/cc732412(WS.10).aspx ). With this change implemented, enabling a Web Garden is a piece of cake really ;-) Hope this helps! Hi Fredrik,

in the blog you state: ” … Do not use Web Garden unless you know what you are doing. …”

In fact, it’s not quite so difficult to implement a Web Garden with EpiServer. All thanks to Microsoft’s own ASP.NET State Service.

The main problem with Web Gardens and EpiServer is session state information.
E.g. if you log on to the CMS while your request is being handled by IIS worker process (A) and perform an action in the CMS which is handled by IIS worker process (B), you will get prompted to login again.
Not really a workable environment.

With the ASP.NET State Service it’s fairly simple to handle session information outside of the IIS worker processes. It only requires the service to be started (it ships with Windows Server out of the box) and the web.config to be altered to use it (See: http://technet.microsoft.com/nl-nl/library/cc732412(WS.10).aspx ).

With this change implemented, enabling a Web Garden is a piece of cake really ;-)

Hope this helps!

]]> By: Patrik Almqvist http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-3180 Patrik Almqvist Wed, 18 Feb 2009 15:30:50 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-3180 Thanks a lot!! Thanks a lot!!

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-3176 Fredrik Haglund Wed, 18 Feb 2009 14:31:07 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-3176 Ah... sorry! The reason is that there are installers that expect that both the Default Application Pool and the Default Web Site exist, otherwise they fail. There are olso a risk that an installer modifies the first pool or web site. So that is why you should leave them in place and not use them. If you used Cassini in Visual Studio for debugging it did also picks up settings from the default web site that affects the site you are debugging. Ah… sorry! The reason is that there are installers that expect that both the Default Application Pool and the Default Web Site exist, otherwise they fail. There are olso a risk that an installer modifies the first pool or web site. So that is why you should leave them in place and not use them.

If you used Cassini in Visual Studio for debugging it did also picks up settings from the default web site that affects the site you are debugging.

]]> By: Patrik Almqvist http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-3175 Patrik Almqvist Wed, 18 Feb 2009 13:33:02 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-3175 Great article, though I have a question.. You write about DefaultApplictionPool: "Do not use it and do NOT delete it (even if you plan to never use it). Create your own pool instead..." bur you do not explain why!? Maybe it's obvious, and just lack of knowledge from my side, but would very much like to know why. Great article, though I have a question.. You write about DefaultApplictionPool: “Do not use it and do NOT delete it (even if you plan to never use it). Create your own pool instead…” bur you do not explain why!? Maybe it’s obvious, and just lack of knowledge from my side, but would very much like to know why.

]]> By: Björn Gullander http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-2251 Björn Gullander Wed, 05 Mar 2008 10:31:29 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-2251 Good article that handles some of these assembly loading problems that can be a horror to resolve. Is there any case when the bind redirect does not work? I have a case where a 3rd-party component uses version 4.61.0.83 of Episerver.dll but in our codebase we use version 4.61.3.83. We have added an assembly redirect in the web.config but still we get the yellow screen telling that the 3rd-party application wants the earlier version. Is there any other way to force the 3rd-party application to use version 4.61.3.83 ? Or is my only solution to ask for a new dll referencing the correct version from our partner? Good article that handles some of these assembly loading problems that can be a horror to resolve.

Is there any case when the bind redirect does not work? I have a case where a 3rd-party component uses version 4.61.0.83 of Episerver.dll but in our codebase we use version 4.61.3.83.

We have added an assembly redirect in the web.config but still we get the yellow screen telling that the 3rd-party application wants the earlier version.

Is there any other way to force the 3rd-party application to use version 4.61.3.83 ?

Or is my only solution to ask for a new dll referencing the correct version from our partner?

]]> By: Mattias Nordgren http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/comment-page-1/#comment-2172 Mattias Nordgren Tue, 05 Feb 2008 11:42:25 +0000 http://blog.fredrikhaglund.se/blog/2008/02/01/performance-tuning-and-optimization-of-episerver/#comment-2172 Great article! Great article!

]]>