Ez 3.7.2 and PHP-accelerating

Author Message

Steph A

Tuesday 24 January 2006 11:57:29 pm

I was just wondering what kind a PHP-accelerator to use for 3.7.2 that supports PHP 4.4.1?

I am currently running FreeBSD 5.4 without any accelerators - and the speed is painfully slow. 10 sec loadtime on a dedicated server... :)

Ɓukasz Serwatka

Wednesday 25 January 2006 12:03:03 am

Hi Steph,

I have been working with IonCube, APC and eAccelerator. The last one had the best performance. But your 10s is really to much, I suspecting that problem is somewhere else. PHP Accelerator can help, but don't expect performance boost from 10s to 0,12s.

Take a look at this topic:

http://ez.no/community/forum/general/ez_speed_optimisation_faq/re_ez_speed_optimisation_faq__14

http://ez.no/community/forum/install_configuration/ez_publish_performance

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Steph A

Wednesday 25 January 2006 1:45:11 am

Thanx for the suggestion. I have fixed some server issues - and now the loadtime is about 1.4 sec ... still not too fast. Havent got too many nodes either, and the templatecode is pretty simple....

I had someone to install a php-accelerator, but and they said that there where some version conflict, and that I could not use the accelarator with php 4.4.1...

I think they tried to install the accelerator from www.php-accelerator.co.uk ... is there any problem getting a accelerator to php 4.4.1?

Any to recommend?

Thanx..

Paul Borgermans

Wednesday 25 January 2006 2:58:42 am

Try eaccelerator, slightly better performance:

http://eaccelerator.net/

I installed (compiled) and tested on 3.7.2 with PHP 4.4.0 (64 bit)

hth

--paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Sebastian Picklum

Thursday 26 January 2006 12:29:13 pm

I hope the following information is still valid: with FreeBSD Version 5.4:
Please notice that FreeBSD is a performance killer itself, since it does a stat()-call for on every file access for every directory level. e.g. /home/youruser/public_html/ezpublish/index.php would result in 5 stat() calls.
You can boost performance by placing ezpublish direct under the root directory or by using Linux as server os.

Regards

Sebastian

sp@php.net

Xavier Dutoit

Thursday 26 January 2006 11:51:53 pm

Hi,

I know that Gabriel is into BSD and from what I heard, he's happy with the performance, at least better than 10 seconds to load a page ;)

Don't know if it's related but if I'm right he uses XFS.

Gabriel, over to you...

X+

http://www.sydesy.com

Gabriel Ambuehl

Friday 27 January 2006 12:08:51 am

Actually, I had sub 1 second load times on FreeBSD 4.11 without eaccelerator and sub 0.2s with eaccelerator. There should be accelerators in the ports tree IIRC. (I think latest eaccelerator supports PHP 4.4)

Visit http://triligon.org

Steph A

Sunday 29 January 2006 7:23:15 am

Thanx for all inputs guys. I still use FreeBSD 5.4 - but managed to get the loadtime down to 0.14 sec with eAccelerator :D

Now I`m happy... :)

If anyone was wondering about hard/software:
Apache/2.1.4 (FreeBSD) PHP/4.4.1
AMD Sempron(tm) 2400+ (686-class CPU) 1666.49- MHz RAM: 239,94 MB

Gabriel Ambuehl

Sunday 29 January 2006 7:31:31 am

That machine ss awfully low on RAM. 512 or more (preferably 1G+) wouldn't hurt at all under load.

But the times seem ok.

Visit http://triligon.org

Steph A

Sunday 29 January 2006 7:50:29 am

Yes I know its low on ram, but for now I just use this as develop-space. When I go live I will upgrade it as needed :)

But still, 0,14sec and often lower is not too bad - or what?

Gabriel Ambuehl

Sunday 29 January 2006 7:53:30 am

That's rather good, actually.

Visit http://triligon.org

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 11:24:36
Script start
Timing: Jan 18 2025 11:24:36
Module start 'layout'
Timing: Jan 18 2025 11:24:36
Module start 'content'
Timing: Jan 18 2025 11:24:36
Module end 'content'
Timing: Jan 18 2025 11:24:36
Script end

Main resources:

Total runtime0.0157 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0051 588.0313152.6406
Module start 'layout' 0.00510.0034 740.671939.4766
Module start 'content' 0.00850.0050 780.1484101.3516
Module end 'content' 0.01350.0022 881.500042.3047
Script end 0.0157  923.8047 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002616.5412140.0002
Check MTime0.00127.4279140.0001
Mysql Total
Database connection0.00074.376510.0007
Mysqli_queries0.003220.077230.0011
Looping result0.00000.089310.0000
Template Total0.001911.910.0019
Template load0.00106.561710.0010
Template processing0.00085.322910.0008
Override
Cache load0.00084.941310.0008
General
dbfile0.00021.443280.0000
String conversion0.00000.043940.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs