3 ms·
No, actually MySQL was the remainder (~150ms). WordPress wasn't updating the cache; I mention that because 700ms is painfully slow, once all the JS and ads run
by juliangregorian 12y ago
No, actually MySQL was the remainder (~150ms).
WordPress wasn't updating the cache; I mention that because 700ms is painfully slow, once all the JS and ads run load time can cross 2 full seconds. The cache becomes the only acceptable way to run it in production.
New Relic actually provides a breakdown of how much time was spent in each function; while I don't remember offhand what that was, there wasn't any low-hanging fruit that could be optimized.