Portal Engine
Version 2.x > Portal Engine > Performance View modes: 
User avatar
Member
Member
timbertens - 11/24/2006 10:03:15 AM
   
Performance
Hi,

compared to the version 1.9 we notice that the speed of the websites developed (simular look and features) in 2.0(a) is a lot slower. Is there some workaround, good practices or will it be reviewed in one of the next versions?

reagards,
Tim.

User avatar
Guest
admin - 11/26/2006 11:18:21 AM
   
Re: Performance
Hi Tim,

Thank you for your message. Yes, we have made many optimizations in version 2.0b which will be soon released and we have added a new full-page caching mode that increases the performance approximately ten-times.

Best Regards,

User avatar
Member
Member
ericcone - 12/20/2006 5:58:39 AM
   
Re: Performance
The problem is with the VirtualPathProvider & JIT compiling. Using the sample corporate site, it takes an average of 2.5 seconds to compile and display a page. If you move all of the controls to the harddrive the time gets reduced to .4 seconds.

I know the VirtualPathProvider is "cool" but I wouldn't recommend it for ascx files. You don't gain the benefits of compiled code because each request would recompile the code. May be I'm missing something in Kentico, is there a good reason for having the controls in the DB? Do you change the controls per page or use?

With 2.0B you implement output caching which helps to mask the issue. Using output caching can be a problem for some (content editors get confused & servers need more RAM).

Using SQL profiler you can see that a page request shows around 175 queries that do the same thing over and over again. Most of the queries are against view_pageinfo and two SPs. It would be nice to cache or push this data to the webserver. Otherwise, the SQL Server gets hammered for no reason.

Thanks,
Eric

User avatar
Guest
admin - 12/20/2006 6:39:10 AM
   
Re: Performance
Hi Eric,

Thank you for your valuable feedback. We have optimized the SQL Server access in the 2.1 version (that will be soon available) so that it minimizes the number of queries, which greatly improves the performance even without full-page caching.

We used the VirtualPathProvider not because it's cool, but because of requests of customers who had problems with editing of ASCX transformations under Visual Source Safe and we also wanted to make the product run without disk write permissions. We will try to optimize this and we also plan to allow developers to save the ASCX files (layouts or transformations)on the local disk where they can be both edited using VS and they will also provide a better performance.

We are constantly working on performance improvements in each new version and we will sure appreciate any other feedback and suggestions.

Best Regards,

User avatar
Member
Member
ericcone - 12/21/2006 5:11:35 AM
   
Re: Performance
Hey Petr,

Your product is a pretty neat CMS. It has a great price for everything that it offers. I was simply stating a few of the (for lack of a better term) weaknesses in the model. I look forward to seeing 2.1 when it comes out, do you have a timeframe?

The VPP is really a neat way to solve those problems. I'd just prefer to see you save the files or allow them to be saved to the local disk. I'm not as worried about editing them via VS as much as I'm worried about performance.

At worst, Kentico CMS is a great CMS framework for developers to use to implement webparts on top of.

If you are looking for ideas, I've got tons.

1. Allow documents to be serialized(XML) after saves to improve performance.
2. Allow drag and drop designing. 2.0B was a nice step in that direction with WYSIWYG designing.
3. Improve the included webparts or open the source to them. It looks like they are compiled into an assembly.
4. Allow one piece of content(products for example) to be used under multiple folders or sites.
5. Implement Lucene.Net for searching.
6. More reports for the newsletters.
7. Multi-part newsletters (Text & HTML).
8. A third-party page of webparts that support Kentico. Forums, WebBlogs, Classifieds, Product Reviews,... could all be built by someone else.
9. An API/webservice for logins.

I'd be more than willing to help you with some of the coding.

Thanks,
Eric

User avatar
Guest
admin - 12/23/2006 11:30:15 AM
   
Re: Performance
Hi Eric,

Thank you very much for your valuable feedback. We will try to follow it in the next releases.

Version 2.1 will bring improvements in layout and transformation editing (you will be able to save them on the disk for better performance and for comfortable editing in Visual Studio or other external editor).

Unfortunately, we had to postpone the 2.1 release to the middle of January so that we can implement all top priority requirements.

Thank you again.

Best Regards,

User avatar
Member
Member
ericcone - 1/10/2007 6:17:59 PM
   
Re: Performance
Is Version 2.1 still going to be released in the middle of January?

Regards,
Eric

User avatar
Guest
admin - 1/20/2007 6:06:14 PM
   
Re: Performance
I'm sorry, we had to postpone the release to January 26.

Regards,