Hardware requirements?

Tuesday 25 November 2003 4:06:17 am

Hi,
I hope to get some advice regarding hardware requirements for ez3.

I am planning to launch four separate websites, running on one eZ installation, with the same Db.

There will be an initial load of approx. 6000 pageviews per day and up to 500 pageviews in the most intense hour each day.

What is your experience of hardware requirements? What would be sufficient to run these websites?

Also, is there any difference in performance between Win2K and Linux when running eZ?

All ideas and suggestions appreciated!

Regards,
Nicklas Lundgren

Tuesday 25 November 2003 7:18:03 am

Thanks for the suggestion, Tony,

However, would you please be more specific when it comes to "write the site correctly"?

For example, one of the sites use a dynamic menu in the left column. Since it alters depending on where in the site the user is, it cant be viewcached, I suppose, so I have disabled viewcache in this template.
The template reads titles of subfolders and generates the menu on the fly. Would you do this in any other way?

Maybee this is why I get accesstimes of 1-2 seconds per pageview on a 2.4ghz windows server with mmcache, template cache, template compile, process cache and viewcache enabled and nodetreecaching disabled.

Any ideas on how to improve the performance?

Regards,
Nicklas Lundgren

Tuesday 25 November 2003 8:28:17 am

Niklas,

to speed up your site you need to use cache-blocks in pagelayout. This will boost your pages very much. If there is no personalized content on your site you should see something like 0.1-0.2 seconds pr page ( cached ) on the hardware you describe.

See the demo packages which comes with eZ publish 3.3 Beta 1 tomorrow. They use cache blocks to speed up page processing.

--bård

Documentation: http://ez.no/doc

Wednesday 26 November 2003 1:33:46 am

>>cache-blocks
The knack here is to use them on the code that does not contain user state specific information.
So you should not use on login boxes, name displays etc. But you can use on items that are page state specific such as navigation, content pages etc.

They really speed things up but need some tweaking to get it just right.

Some cache block info pages
http://ez.no/developer/ez_publish_3/documentation/incoming/how_to_set_cache_expire_time_or_disable_cache_in_template
http://ez.no/developer/ez_publish_3/documentation/development/libraries/ez_template/functions/function_list (scroll down a bit to find)

--Good luck

tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Wednesday 26 November 2003 3:31:36 pm

For Cache-Blocks:
Bard is right, they boost speed a lot, but it's tricky to use them sometimes.
We use them to cache several navigation elements (incl. a tree navigator), but the Cache-Keys for this block is something like
{ URI and User Group }, because the tree depends on the current page (obviously) and sometimes depends on the user group (better: Roles), that the user is in to decide, wheter some folders are visible or not.

Marco
http://www.hyperroad-design.com