|
Pocha Bartok
|
Sunday 28 September 2008 3:54:59 am
Hello, I am a new EZ Publish user. I own a rather large (6,000 daily unique visitors) website about gaming, content-centered, with reviews, articles, interviews, media files, and so on. So far, I have loved everything I have seen in EZ Publish, but I have a couple of questions.
1. Performance - How does EZ Publish behave on large traffic websites? Is it a resource hog or has it solid a caching system (even better in our case would be static files, since most articles, once edited, do not need to be updated at each visitor's view)? Can anybody give me real life experience?
2. Integration - We NEED to have EZ Publish integrated with vBulletin. First, because our users cannot leave without the dozens of custom add-ons we have done for vBulletin, second because we are active developers in the vBulletin community and prefer to keep working on it also for our websites, that can thus become a showcase of our work. More of an integration, probably, all we need is a solid and not intensive bridge - is it easily doable or EZ Publish's user access system is very rigid (like in many other CMS we have worked with...).
3. Finally, how fast is the development environment to develop and deploy solid AJAX (yeah, stupid acronym) add-ons in your experience? Thanks, Poch
|
|
Gaetano Giunta
|
Sunday 28 September 2008 1:09:32 pm
1 - there are many caching layers in eZPublish that will allow to squeeze the best performances out of your setup.
Just make sure to enable as many layers as you can, and to correctly configure your installation for it - with some many knobs to twist, it is sometimes hard to get everything correct.
Also make sure your template code is optimized for the traffic. Simple guidelines include:
- there should be as little data fetches as possible, and all those fetches should use filtering options instead of fetching too much data and filtering it later
- use cache-blocks wisely: they can make page loading much faster, but using too many of them kills performances
You will find many optimization tips on the site (articles) and in the forums. Other optimization tips include activating the eZ static cache (but that has a big impact on the design of your html pages, as all dynamic parts will have to be moved to ajax), and putting a reverse proxy in front of your eZ Publish server. 2 - integration with bulletin systems has been done many times, so it is surely possible. The easiest way, but by long not the only one, is probably to create a sso handler on one hand, and have a user-db sync script running in the background. 3 - no direct experience to give you an estimate about ease of development, sorry. But there are a few ajaxy extensions on projects.ez.no you can check out
Principal Consultant International Business
Member of the Community Project Board
|