tags:

views:

265

answers:

3

Our team has just started developing for the Sitecore CMS.

We find that after every code change (.cs file) the app needs to restart and sitecore's restarting takes us up to 2.5 or 3 minutes. Our local pc's dev env communicates with a distant database. Aside from increasing our bandwidth to the database, are there ways speed up a sitecore restart (turn off caching etc.)

Are sitecore developers typically using IIS or VS's web dev env?

I assume using IIS would still present the same issue of restarting sitecore after every change?

+4  A: 

Maybe you can use CodeFile rather than CodeBehind. See section 2.2.3 of our Presentation Component Cookbook: http://sdn.sitecore.net/upload/sitecore6/presentationcomponent%5Fcookbook-a4.pdf#search=%22codefile%22 Using this means that you never have to recompile a single page. Of course Sitecore hooks require recompilation.

Kind regards,

Alex de Groot

Sitecore Solution Architect

Alex de Groot
Alex, Thanks so much, I'll check it out! I read your blog, and was actually thinking of trying to obtain your email as my next course of action :)
David
+1  A: 

You can also add optimizeCompilations="true" to the <compilation> section in web.config iy you run on webdev or IIS 7/7.5 with .NET 3.5 SP1 (or a hotfix from MS). More info here: http://msdn.microsoft.com/en-us/library/ms366723.aspx.

pbering
+3  A: 

Our local pc's dev env communicates with a distant database.

This is likely a big cause of the slow down. At least until its data cache gets built up, Sitecore does require quite a bit of DB communication. Development cycles will prevent it from building up any sort of useful data cache, since you're constantly restarting. I would suggest running a database closer to your development environment and use packages, or look into Team Development for Sitecore (http://www.hhogdev.com/products/team-development-for-sitecore.aspx).

techphoria414
I would have to second this remark. Sitecore retrieves a lot of data over the wire at startup to repopulate it's item caches. Try developing against a local database and I'd be willing to bet that you see marked improvement in your restart times after a build.
aweber1