Premature Optimization Mistakes

Ilia Alshanetsky (Oct 20, 2009)
Talk at ZendCon 2009 (English - US)

Rating: 5 of 5

One of the thing that many people want to have is fast code as it allows handling of more data/clients with less resources, saving money and improving your overall efficiencies. However, premature optimization can often result in broken code, enormous amount of wasted time and missed deadlines. This talk will not only explain the common errors, but also offer easy performance solutions.

 
Comments closed.

Comments

Rating: 5 of 5

Oct 20, 2009, 23:58 by smalyshev

good talk!

Rating: 5 of 5

Oct 21, 2009, 00:14 by jimplush

This was my favorite talk so far. He was like a machine and right into the details. Great talk, learned a lot

Rating: 5 of 5

Oct 21, 2009, 00:25 by RobertGonzalez

I'm not sure Ilia ever stops talking in his presentations. Not that it matters, his presentation was full of useful concepts, gotchas and best practices. Very informative, to the point that before I left the presentation, I had already deployed APC on one of my more popular site's server.

Rating: 5 of 5

Oct 21, 2009, 15:50 by Claudia

Great talk. Very informative. Great speaker.

Rating: 5 of 5

Oct 21, 2009, 17:00 by nbroers

Rapid delivery and engaging, my favorite talk so far.

Rating: 5 of 5

Oct 22, 2009, 23:07 by Anonymous

This should have been a keynote

Rating: 5 of 5

Oct 23, 2009, 05:22 by simplemotives

I agree with "ANONYMOUS", this should have been a keynote. Ilia definitely earned several fans.

Rating: 5 of 5

Oct 24, 2009, 05:22 by Anonymous

Undoubtedly Ilia was one of the best speakers. Most of his sessions were technical and that's what I expected at a World PHP Conference.

Questions:
1) output_buffering = On is that helpful really?
2) SQL Caching? Is it like dumping daily data into a table to generate reports easily instead of querying summaries from various tables?

Speaker comment:

Oct 24, 2009, 13:31 by ilia

The "output_buffering" buffering setting is helpful (especially when set a high value) when you are sending fair quantity of large PHP generated pages to the user.

"SQL Caching" could mean many different things, such as sql de-normalization for reporting purposes, etc... However what I was referring to was storage of SQL results in memory via memcache or apc, so that database does not need to be queried every single time.

Is Spam

© Joind.in 2010