However, one thing that I was struggling with was the loading time of the Experience editor. You could launch it then wait for 10 minutes without being able to do anything. After a bit of research I found out an really great post from Kam Figy: http://kamsar.net/index.php/2015/02/sitecore-8-experience-editor-performance-optimization/
So it seems like there is a SPEAK precompilation happening. So there is a trade:
If you comment these out, you trade having the SPEAK interfaces come up slower the first time (because they are not precompiled) for faster initial startup time (because you skip precompiling)
The precompiling would be good when the application is running on the production server. However, during the development stage we are always compiling our code and restarting the App Pool... So when doing dev work I guess the poor and cons are quite simple: we would definitely go for a faster startup...
I went for the option 1:
Edit the file: /App_Config/Include/Sitecore.Speak.config
comment out the section for the initialise pipeline:/sitecore/shell/client/Business Component Library
Edit the file: /App_Config/Include/ContentTesting/Sitecore.ContentTesting.config
comment out the section for the initialise pipeline:
/sitecore/shell/client/Applications/ContentTesting
This worked quite well on development environment however I would leave those pipelines on the production envrionment as the application would be running for a longer period without restarting the app pool...
