Comments on: 3 simple steps to boost performance of a PHP web application

By: Lukasz Kujawa

Lukasz Kujawa — Thu, 20 Jun 2013 09:02:12 +0000

I guess that depends on settings. If you have profiling ON by default than you can expect trouble. If you have the remote debugging on there is a security issue. Appart fron that I wouldn’t think so but I have no data to support it so it’s only an assumption

LikeLike

By: mixdev

mixdev — Tue, 18 Jun 2013 17:08:54 +0000

Won’t some overhead kick-in with XDebug on production?

LikeLike

By: Lukasz Kujawa

Lukasz Kujawa — Fri, 24 May 2013 09:14:46 +0000

Good point, thank you. I used to blindly copy that function for years.

LikeLike

By: Mariusz Kujawski

Mariusz Kujawski — Fri, 24 May 2013 08:44:31 +0000

microtime(true)?

LikeLike

By: Lukasz Kujawa

Lukasz Kujawa — Fri, 24 May 2013 08:24:37 +0000

Hello Wojtek, thank you for your comment. Breaking routes is a good idea but for this particular application hard to do. We need routes from various modules to build links with the URL helper.

Could you please tell more about the issue with APC? 5ms is indeed very slow for pulling data form memory. Is it because of concurrency and locking or there are some other reasons?

LikeLike

By: Wojtek

Wojtek — Thu, 23 May 2013 15:43:05 +0000

A easy way to improve your Zend 1 Routing is to (if possible) split your app in main index.php and load different, module-specific Application class with different set of routes. It also means that adding new routes will not slow down other parts of your app!

APC is your friend – but be careful, and always benchmark your changes. Fetching objects from APC can take more then 5ms in some cases, it might be more then initialising PHP object with config array retrieved from APC.

Also, it’s good to make sure that there are no `require_once` in your code, there is a lot of it in Zend 1. Even with `apc.stat = 0` require once will hit disk and stat the file!

And finally, use XDebug regularly on your production environment!

LikeLike