Talk in English - US at Midwest PHP 2016
Short URL: https://joind.in/talk/73910
(QR-Code (opens in new window))
Caching Best Practices
Comments are closed.
Ecxellent talk! I would like to hear a little about persistent cache engines
Interesting, valuable information presented clearly and energetically.
A little long on content. Note sure it's necessary to explain each method in such detail.
As a speaker, Eli is confident and entertaining. This talk however should've been simply titled Intro to Memcached, as it mainly consisted of enumerating the various php methods for interacting with memcache, along with some "don't do that" statements - usually with little or no explanation. For example he states that filesystem caching is very common, but a bad idea, and then moves on. I can speculate that this is due to disk i/o speeds, yet I'm skeptical of that in the context of a php application. He didn't even mention Redis, which is often used in place of memcached. His code samples were crazy nested loops and conditionals, which in combination with the examples from Digg gave the talk a feeling of being outdated php4-era information.
I was hoping to learn more about OPCache since I've been having issues with it on some of our client sites. But the information about memcached was good ... we've been thinking about using it on our servers but aren't sure where to start.
Eli covered both real world and theoretical examples to clearly explain some of the common pitfalls of caching. Extremely valuable hour of content!
Eli was a great speaker as usual, the talk however was not as advertised, it was mostly focused on using the memcached api.
In the future, I'd like this talk to cover better caching principles and techniques instead of focusing on API details, some modern OOP code wouldn't hurt too.
Like it a lot. Filled up a few holes on my current knowledge of APCu and Memcached.
Very straight forward and useful.
A lot of "Don't do that" without proper justification... but time was very tight. So can't be blamed.
This talk was at a good depth. It gave practical solutions and had real numbers for how caching improves things.
An architectural diagram could have helped everybody fly in from a mile high down into the code.