Has anybody had any experience with this.. ??

http://www.php-accelerator.co.uk/

I did search here but nothing showed up..

wow! that's a news to me. looks great. must try and see how it goes. it's relatively a new product.

I'm also interested in trying this out. To see how things were going, I subscribed to the mailing list. It's pretty interesting. There are a number of issues (bugs?) that are scaring me away from using it at the present. However, it seems to hold a lot of promise. I'm going to continue monitoring the mailing list and wait till it seems stable enough for me to try out. I have enough problems with my own bugs without making it even more difficult for myself.

I'm also interested in hearing about the experiences of others with this package.

I have good resukts using jpcache.

http://www.jpcache.com/main.php?content=benchmark
http://www.jpcache.com/

I dumped APC Cache in favor of PHP Accelerator...

I find it to be a bit faster :D

Originally posted by felix220
Has anybody had any experience with this.. ??

http://www.php-accelerator.co.uk/

I did search here but nothing showed up.. Well, there's some stuff here:
http://www.webhostingtalk.com/showthread.php?s=&threadid=41814

And it's a wonderful tool :)

Hi,

Thanks for the interest in PHPA in the thread :)

Just to add some info, PHPA actually isn't that new - well less than a year old, but a lot can happen in a year. You can check the history page on my site for a little journal of the timeline leading up to the first release.

Bug wise, most people should actually be fine with it, and there are some rather large sites using it now - e.g. www.disboards.com for a large vbulletin site. One of the problems is that PHP 4.1.2 is prone to core dumping (without phpa installed) on some systems - aparantly it's a mysql/php problem - and that puts tools such as phpa at a disadvantage. However phpa has crash detection built in, and attempts to be tolerant to unstable sites.

1.2p5 is also due soonish and has most of the features in place for that release, although there are still a few more things that I'm going to add to that release.

Performance wise, you should roughly match or even beat Zend Accelerator, and due to the different internal design of PHPA, certainly beat APC and the other free caches.

Concerning jpcache, that's an entirely different type of product, and targets caching of the output. PHPA effectively caches the input. The cost of reading and compiling PHP script files can be significant, and that's what PHPA and other similar caches eliminate. PHPA is exploiting the fact that most scripts never change from one request to the next, and so the preprocessing that PHP performs every time isn't changing either. Your sites are just as dynamic as before.

JPCache exploits the fact that for some pages, output never changes often. So whilst you may have generated the page programmatically, the output will be the same every request, and so you could cache the html output. Depending on the cache, you have to be careful with output caching to ensure that you don't lose any necessary dynamic behaviour.

nick

Originally posted by phpa
Hi,

Thanks for the interest in PHPA in the thread :)

Just to add some info, PHPA actually isn't that new - well less than a year old, but a lot can happen in a year. You can check the history page on my site for a little journal of the timeline leading up to the first release.

Bug wise, most people should actually be fine with it, and there are some rather large sites using it now - e.g. www.disboards.com for a large vbulletin site. One of the problems is that PHP 4.1.2 is prone to core dumping (without phpa installed) on some systems - aparantly it's a mysql/php problem - and that puts tools such as phpa at a disadvantage. However phpa has crash detection built in, and attempts to be tolerant to unstable sites.

1.2p5 is also due soonish and has most of the features in place for that release, although there are still a few more things that I'm going to add to that release.

Performance wise, you should roughly match or even beat Zend Accelerator, and due to the different internal design of PHPA, certainly beat APC and the other free caches.

Concerning jpcache, that's an entirely different type of product, and targets caching of the output. PHPA effectively caches the input. The cost of reading and compiling PHP script files can be significant, and that's what PHPA and other similar caches eliminate. PHPA is exploiting the fact that most scripts never change from one request to the next, and so the preprocessing that PHP performs every time isn't changing either. Your sites are just as dynamic as before.

JPCache exploits the fact that for some pages, output never changes often. So whilst you may have generated the page programmatically, the output will be the same every request, and so you could cache the html output. Depending on the cache, you have to be careful with output caching to ensure that you don't lose any necessary dynamic behaviour.

nick hey nick :wavey: