|
Author
|
Message
|
|
Kåre Køhler Høvik
|
Saturday 11 March 2006 11:48:16 pm
Hi We recommend the latest stable version of APC - http://pecl.php.net/package/APC
Kåre Høvik
|
|
Veselin Penchev
|
Friday 28 April 2006 11:51:52 am
Hi,
We use turck-mmcache on our page.
The change in speed was obvious.
/the server is Debian-Linux , ez 3.4/
|
|
André R.
|
Friday 28 April 2006 12:01:24 pm
if you are using Turck, you might want to test out http://eaccelerator.net/ witch is based on turck.
While turck haven't been updated in 2-3 years, eaccelerator are still improving their code. but both Turck and Eaccelerator should be a better choice then apc, as APC is only a php cacher.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
|
Theodoros Papageorgiou
|
Friday 12 May 2006 1:35:48 pm
I use eaccelerator 0.9.5 beta, php-4.4.2 for about two months on my server without any problems.
WEBWiZ
Web Development
http://www.webwiz.gr
|
|
Simon Lynch
|
Tuesday 06 June 2006 6:19:45 am
We have been using APC (on FreeBSD 5.4, Apache 2.0) for quite a while and things were more or less OK. We think we have hit some limits (probably a recent code build which added and extended templates) and so have the problem of increasing cache memory. This makes the apaches grow and seems to be slower. We have been trying to exclude some of the cached scripts we are generating using the filters in APC and cannot make it work (at all). Just wondering if anyone has tried this and, if so, they can post the filter expression they have been using (as well as the rest of the php.ini directives for APC they are using). I would post ours, but I am not sure they are really going to help anyone - given we have had to turn the thing off as it kept blowing up and will have a very, very slow server until we work out how to fix this. I guess some instructions on APC optimisation would be of benefit for anyone using EZ and this accelerator for a large implementation. The benefits are there and APC means that EZ can be implemented under traffic without exploding servers.
|
|
Simon Lynch
|
Wednesday 07 June 2006 2:01:13 am
We have come to the conclusion that the best way of avoiding APC cache overload is to filter out the scripts in the EZ file cache (for us this is a lot of cached template-blocks and other bits and pieces). This means that APC caches the main EZ scripts and seems to work pretty well. We are still running out of allocated space, but probably need to increase it and tweak some of the other settings. We are using the following directive in php.ini: apc.filters = "-cache.*\.php" We could not get APC to accept more than one filter, it seems to ignore sequential comma-separated filters for us, even though we have seen some examples of other people making them work in forums.
|
|
Tony Wood
|
Wednesday 07 June 2006 12:43:56 pm
Hi, We use APC and have found it to be reliable. 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
|
|
Kim Johansen
|
Wednesday 07 June 2006 1:15:09 pm
If you need good performance, eaccelerator is better then APC. Its also importent to think about other things, like mysql and apahce.
mysql: innodb with socket is faster than myisam with socket or tcp/ip. caching is also very importent.
apache/php: php as a module is faster then static.
--
Med vennlig hilsen / Best regards
Kim Johansen - WebDeal AS
Teknologiveien 22 - 2815 Gjøvik - NORWAY
Phone: +47 61 13 16 50 - ICQ: 262860894
E-mail: kim@webdeal.no - URL: www.webdealhosting.com
Try out Free eZ Publish 4.0 Trial Hosting for 14 days:
http://webdealhosting.com/ez-publish-trial-hosting
High quality eZ Publish Hosting since 2001!
|
|
Paul Borgermans
|
Wednesday 07 June 2006 2:48:56 pm
I also like eAccelerator more (performance), but OK, I'm Belgian just as Bart, currently the main developer. Both accelerators are a bit fragile with respect to the long-term development horizon. Let's see how the open source paradigm works here --paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Linh Vu
|
Thursday 08 June 2006 1:01:35 am
I'm using eAccelerator for PHP 4.4. PHP6 (which will work with ezPublish 4.0) will have a built-in opcode cache, I believe, so that will cancel the need for a 3rd party accelerator.
If I had more time, I would write less code.
|
|
Vjeran Vlahovic
|
Wednesday 21 June 2006 6:36:48 pm
Hi all! I am also using eAccelerator but wondering how to setup eaccelerator.shm_size parameter. Default value for this is 16 MB and it is probably to low... Should eaccelerator.shm_size="128" be enough? Or even more? I run several ez installations on dedicated machine with 1 GB of RAM.
http://www.netgen.hr/eng
|
|
Vjeran Vlahovic
|
Friday 23 June 2006 7:28:10 am
Here's one article about comparison of APC and eAccelerator: http://www.ipersec.com/index.php?q=en/bench_ea_vs_apc&page=0%2C0 Also, today I have found out that it's better not to have Zend Optimzier (i need the encoder) along with the eAccelerator at the same time (from the eAccelerator trouble shooting doc): eAccelerator is has been reported to work with Zend Optimizer's loader. Zend Optimizer must be installed after eAccelerator in php.ini so it's loaded after eAccelerator. If you don't use scripts encoded with Zend Encoder then we do not recommend to install Zend Optimizer with eAccelerator, it won't give you any extra performance.
http://www.netgen.hr/eng
|
