running late! (great lunch with folks from B’ham)
particular page that’s running slow – exclusive
I don’t understand what’s going on.
80ms content type info – why is it being called so many times – look at time spent vs how many times it was called.
this is like the opposite of the last session – no pretty slides, lots and lots of examples. equally baffling, tho.
take a look at memcache.
(it occurs to me that I’m going to want to take a big chunk of time this fall to really clean up the site.)
likes to see mysql problems float to the top because they’re easier to deal with than other problems.
can see exactly which queries are the problem.
this is all about how to identify problems, not how to solve them, which is fine. worst thing for me is just being baffled by why there’s even a problem.
SO FRUSTRATED that I missed how to get this up and running.
Devel query logger?
Google “[function name] performance” and look for patches, etc.
Ok, so XHProf is an extension for PHP. what’s going to be involved in getting that up and running?
am I caching Views correctly?
all about finding low-hanging fruit and/or biggest bottleneck.
xdebug – what did he just say was the gui? but xhprof is easier, includes some features
devel query log, views signature – what else does this give you? module problems.
APC? “this are the things that you have already done before this can be useful” – missed some details in his answer to the question that I didn’t actually hear very well. (from webchick?)
so maybe I should look at devel query log FIRST, but this is probably useful too.
is he talking about the xhprof module? or xhprof in devel? xhprof module is coming back to life, I guess; makes more sense than devel integration.
I can’t hear any of the questions, especially since the VACUUM CLEANER IS RUNNING. (so I shut the door.)
q: was originally designed for evaluating a single page – how is this useful for a whole site? that’s why he’s doing work on extending xhprof for drupal. or something. I am genuinely baffled. (once again, sorta wishing I’d gone to a different session. Omega theme might have been handy.)
CPU time and function calls are key info.
(seen on Twitter: Omega has a subtheme wizard! session info at http://omega.cellardoormediagroup.com/)
slow query logger.