3 ms·

The glory of this system is that WP retains their stupid easy install. I suspect they pull down the data for whether a cron needs to be run in an initializing

The glory of this system is that WP retains their stupid easy install. I suspect they pull down the data for whether a cron needs to be run in an initializing query that also pulls down a ton of other data (site name, for example). So in theory, they're only doing a few time comparisons of extra work per request. Also - I haven't looked too deep into WP's implementation, but are they actually doing it on page load? I've seen it in other php software (I believe phpBB) as a 1px image. This kinda solves the caching issues others are talking about...your server might still get hung up, and that picture might never load, but if you're cached properly I think it won't stop anyone from reading. Ignoring the bugs though...I've had my shared hostgator plan handle a couple of top page HN post with no additional caching installed, which makes me think it's probably not a problem for most people running WP. (I just double checked to make sure that's actually true, and it is.)

rmccue 13y ago
> I haven't looked too deep into WP's implementation, but are they actually doing it on page load? On page load (that is, when WP actually runs), WP fires off a non-blocking HTTP request to itself. This runs at maximum once per minute, and shouldn't actually run if you're using Super Cache or similar and hit a cache page.
- jacques_chester 13y ago
  It's non-blocking on the page load, but it still ties up an additional PHP instance.
jacques_chester 13y ago
> So in theory, they're only doing a few time comparisons of extra work per request. And if a plugin has registered a long-running function, you're kinda screwed. > Also - I haven't looked too deep into WP's implementation, but are they actually doing it on page load? Yep. > I've had my shared hostgator plan handle a couple of top page HN post with no additional caching installed, which makes me think it's probably not a problem for most people running WP. HostGator install WP Supercache by default.
- deleted 13y ago
  [deleted]

rmccue 13y ago

> I haven't looked too deep into WP's implementation, but are they actually doing it on page load? On page load (that is, when WP actually runs), WP fires off a non-blocking HTTP request to itself. This runs at maximum once per minute, and shouldn't actually run if you're using Super Cache or similar and hit a cache page.

jacques_chester 13y ago
It's non-blocking on the page load, but it still ties up an additional PHP instance.

jacques_chester 13y ago

> So in theory, they're only doing a few time comparisons of extra work per request. And if a plugin has registered a long-running function, you're kinda screwed. > Also - I haven't looked too deep into WP's implementation, but are they actually doing it on page load? Yep. > I've had my shared hostgator plan handle a couple of top page HN post with no additional caching installed, which makes me think it's probably not a problem for most people running WP. HostGator install WP Supercache by default.

deleted 13y ago
[deleted]