Bug reports Found a bug? Post it here please.
Version 4.x > Bug reports > Kentico CMS is generally slow and unresponsive View modes: 
User avatar
Member
Member
random0xff - 4/14/2009 8:10:03 AM
   
Kentico CMS is generally slow and unresponsive
The backend of Kentico CMS is just too slow. In the CMSDesk, clicking any treenode of the corporate site takes 30+ seconds before it's loaded, if it loads at all. This is with a clean install of Kentico CMS, database and only one site (Corporate ASPX).

Front end is also slooow, showing a news article takes almost one minute.

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 4/14/2009 2:00:11 PM
   
RE:Kentico CMS is generally slow and unresponsive
Hi,

Where are you running your web site? Could you please see this blog post?
Also are you using any caching options?

Best Regards,
Juraj Ondrus

User avatar
Member
Member
random0xff - 4/15/2009 4:40:54 AM
   
RE:Kentico CMS is generally slow and unresponsive
Running from visual studio, default Kentico installation. I'll try the Kentico debugging thing, see where the problem is.

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 4/15/2009 5:00:56 AM
   
RE:Kentico CMS is generally slow and unresponsive
Hi,

Have you tried to run it from IIS? It is obvious that when running it in debug in VS that it is slow - VS have to load many data to the memory and also when perfomring action ond the web, the VS compiler needs to check everything.
When running the live site, in general, it is not recommended to set the debug mode to true. I do not thing that your live site will run on VS server but on IIS server which is much much faster.

Best Regards,
Juraj Ondrus

User avatar
Member
Member
Elijah - 4/29/2009 9:38:46 AM
   
RE:Kentico CMS is generally slow and unresponsive
I have found the admin interface to be quite responsive compared to similar applications of its scale.

Running in debug mode through visual studio will severely impact performance. I always run through IIS. You can even debug through IIS if you set up visual studio to not use the built-in web server.