Comments on: A new job! - but no Symfony

By: Greg Magarshak

Greg Magarshak — Fri, 08 Feb 2008 08:16:51 +0000

gregory at gregory ,net

I found your post on Google, and checked the date — it’s quite recent!

Listen, if you’re looking for a blazing-fast framework that DOES all the main stuff you need from symfony:

* autoloading classes
* importing modules and components
* fancy routing rules
* templates, layouts
* validation and escaping
* MVC architecture

but really really fast, I can give you my framework. I originally developed it exactly because I had the same goals as you — I really liked symfony, but I wanted something that was lightning fast and could be very responsive.

Keep in mind, btw — you can mix symfony with plain PHP files! So if you need a fast ajax response, just don’t use symfony for that particular action, and make it a php file. Also, even if your controller and view code is slow, like in Ruby on Rails, webservers can still be replicated, and your DB will be the bottleneck. So maybe you should jsut stick to symfony.

But if you want to see a really fast framework that does 90% of what you did in symfony, check mine out.

By the way, a ‘hello world with templates and components and routing and autoloading’ executes in 2ms (with APC), unlike symfony’s 80-100ms.

WOOT!

Oh yeah, and write naked SQL with PDO plz. :)

By: Tom

Tom — Mon, 28 Jan 2008 10:05:45 +0000

A little tip, try and setup a tempfs (ram based hd) and have a script copy your symfony files on OS startup. This way you get a blazing fast scriptloading time. Since symfony (and its plugins) use a lot of files, this can nicely increase your performance.

By: Lukas

Lukas — Mon, 21 Jan 2008 09:17:25 +0000

I think with Symfony 1.1, you will find that its much easier to do these sorts of optimizations, that is removing/replacing core components. Anyways, with a bit of hacking on internal classes I managed to get symfony 1.0 to suprisingly good results. I actually did not spend that much time on optimzations and for a fairly high traffic site (a portal that is called for the first request in all Hotels powered by wifi from our client), the bottleneck seems to always be the dedicated authentication hardware or the java backend .. the only things we had to tweak on the frontend were the SOAP call cache into the Java backend and better filtering of applications pretending to be browsers. And in all of those cases it was again not PHP choking, but the backend apps.

By: jo

jo — Mon, 21 Jan 2008 09:16:19 +0000

I wonder why people do so often complain about performance issues concerning
symfony. We have here an single server application running on symfony with about 5 millions PIs.

The only bottleneck we experience is the database interface (we use the standard propel). This is why we use here a mysql master-slave replication.

You might say that 5 millions is not that much. But not too bad neither. Isn’t it?

Cheers