any tips and tricks to speeding Kentico up?

veronica madsen asked on May 10, 2015 00:31

One other issue I am having is that I find it quite slow when running on my desktop with Visual Studio. And I'm on a fast machine with SSD drive and 16 GB RAM. Seems like building and viewing the site takes a really long time. I am running it as a "web application" and I read somewhere that "web sites" runs faster.


Recent Answers

Virgil Carroll answered on May 10, 2015 00:54

Veronica, this is because of the pre-compilation nature of Kentico (or any other .NET app). To really get good performance the application has to be connected to on a consistent basis. This keeps the site in the web server cache and will really speed up performance. I think all of us experience slowness in our dev environment except for the few times we are actually working on the site constantly.

In production (once launched) you can tweak some of the cache settings to better manage your objects and increase performance that way, but in a dev environment you really do not want to do that.

If you are doing compiled code development, there are a couple of good articles on how to better deploy into the environment so the entire web application doesn't completely need to be re-compiled.

Hope that helps.

0 votesVote for this answer Mark as a Correct answer

Charles Matvchuk answered on May 10, 2015 02:08 (last edited on May 10, 2015 02:28)

@Veronica, is there a specific reason you are running it as a web application ? You lose some live functionality with a compiled web app vs. website, check documentation for the differences.

I use it as a website with Visual Studio 2013, spin it up by running it with Ctrl + F5 which runs that application without debugging, this way I can make full code changes. I hit the pages that I will be working on or the web parts etc. I make my changes to the code or markup and just reload them in the browser again, it will recompile just the pages you are touching and their respective web parts, code ,etc. It is much quicker. If you change the web.config or a library, or global code ever it will take a bit longer to compile when you refresh.

Additionally, when I send the site live or if I am working on a production site, I just mirror the entire website down on my development machine. Make the change and just send the pages, web parts, library or class back to the production server after I test it locally. I either just copy the enhancements, changes directly or I export and import such as with modules.

One other thing, it sounds like you are new to Kentico. I had the same uneasiness when I started using Kentico, years ago. The habit is to build your project, hit F5, and test. Back and forth, back and forth. With Kentico, you can still do that, but the project is so large the to run it every time is slow and takes a bit of time, minutes. I only run and debug the application when there is a problem or when I am finally done with changes. Do please read the documentation on website and web applications with Kentico.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on May 10, 2015 18:56

Kentico MVP, Brian McKeiver has a good blog post on some simple things to speed up the debugging. I too, would also question as to why you chose application vs. website.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.