Caching For Cash Dutch PHP Conference – Amsterdam,  June 2009
Head of R&D at  echolibre , pear extraordinaire, published author, party person and an Icelande r
Works at  Jelsoft , php core developer, published author, party person and a Scottish person
 
Identify the performance issues
Analyze the issue
Fix the issue
 
Locate
Diagnose
Recitfy
 
 
 
 
 
APD XDebug
ab Siege Apache Flood Memtrack XHProf GUIMark Hardinfo Bonnie++
 
 
 
 

Cashing For Cash, part 1 DPC 2009

Editor's Notes

  • #9 Websites have more pages than you think. Performance effects are aggregate.
  • #12 Database Buffer Cache Network etc
  • #18 Overloaded databases Badly configured machines NFS / File system contention Solutions: Get a real system administrator Pick the right database for the job Clustered / Proxy databases
  • #19 Missing indexes. Poor schema architecture. Bad database tuning. Selecting too many columns / rows
  • #20 Proxy callout to external services Remote PHP includes REST / AJAX SOAP / RPC calls Solutions: Cache the network calls Design your AJAX so you can easily cache it
  • #21 Image manipulation Encryption system/exec/etc. function calls Solutions Off load work to other machines Gearman and similar are your friends
  • #22 Performing extensive looping text replacements Performing extensive looping in general Badly written Regular Expressions Extensive recursive functionality