Admin and cold start performance

Vote:
 

Is there any way to speed up the episerver editor/admin part?

It seems like theres no bundling happening, and the browser makes roughly 200 requests to show toolbar which is insane! Even when i run the system locally it takes around 8 seconds to just show the basic UI which is horrible. 

The cold boot is also a lot slower than epi 6. Inn epi 6 it was possible to exclude some dlls from the startup, is it possible to do something similar in epi 7.

As a developer i spend probably 60% of my days now just waiting for episerver to start from the last compilation and redraw the UI. 

It's probably something that can't be fixed without access to the source code but hopefully the developers at episerver reads this and realises that they will lose a lot of customers if they dont fix this soon. A pissed off developer can easily remove tens of yearly subscriptions and tens of new customers.

#74841
Sep 09, 2013 17:59
Vote:
 

One way is to exclude some dll from EPiServer Framework scanning process (http://stackoverflow.com/questions/16550827/what-does-forcebinfolderscan-attribute-in-episerverframework-config-file-means/16560302#16560302) but from experience that will not give you significant improvements (unless you have huge list of libraries those really does not contain EPiServer related stuff).

#74844
Sep 09, 2013 21:51
Vote:
 

Hi Tommy!

Which browser are you running? I'm running my development environment with a bit over 1000 request (without any minification/layer packaging) with a load time around 4 seconds in Chrome. With minified layer files I'm done to a bit over 3 seconds. Doing the same thing with Firefox adds a few more seconds so Chrome is currently the main browser for most of our developers.

The times above is given the Alloy demo site with very little content. We know that there are some performance issues when working with sites with large amounts of content and ee are currently working on improving performance for the page tree to speed this up. If you are running with content providers, you might want to know that we are currently working on a performance bug targetted for the next core patch.

#74847
Sep 10, 2013 8:28
Vote:
 

Hi,

one of the key settings is making sure you have enabled optimizeCompilations in web.config. There is also a tool so that you can debug if one of our modules is slowing down your system. We have done a lot of improvements and rewrote the whole scanning process in 7 to make sure its faster, see:

http://world.episerver.com/Blogs/Per-Bjurstrom/Archive/2012/9/EPiServer-7-Startup-Performance/

 

#74850
Sep 10, 2013 10:33
Vote:
 

Im using Chrome as well, but its a bad idea to have that many requests, after all its 1000 files it needs to check file versions, read from cache etc. My harddrive at work is probably the main bottleneck here, an SSD would probably shave most of that time off, but I can't require every customer to upgrade to high-end gaming machine to be able to update their website.

Theres no reason to not bundling all those episerver CSS files and javascripts. One of the most common complaints I get is that the ui is really slow and thats even from people with modern quad core computers that uses chrome.

optimizeCompilations made a big impact, went from about 32 seconds for a complete cold start to about 12. Why isn't it set as default?

Edit: It does seem like it was default but disappeared from the web.config some time ago when switching .net framework to 4.0 istead of 4.5.

#75000
Edited, Sep 13, 2013 14:53
Vote:
 

Just some more information regarding performance and the 7.5 release:

  • 1000 requests should not be the normal scenario for a web site, that's when running the UI with debug scripts that are unminified and unpacked. There are still a bunch of rather unessesary files being loaded due to the fact that we support some legacy dialogs.
  • There has been quite some work for the next release to improve the performance for the user interface, specifically for sites with lots of content.
#76044
Oct 16, 2013 10:04
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.