[wp-meta] [Making WordPress.org] #1116: Site Cloner: Prime mShots cache
Making WordPress.org
noreply at wordpress.org
Thu Jul 9 14:55:47 UTC 2015
#1116: Site Cloner: Prime mShots cache
--------------------------+--------------------------
Reporter: iandunn | Owner:
Type: enhancement | Status: new
Priority: normal | Component: wordcamp.org
Resolution: | Keywords: needs-patch
--------------------------+--------------------------
Description changed by iandunn:
Old description:
> The plugin uses the mShots service to generate the site screenshots, but
> those are built asynchronously when the first request is received, and
> then cached for 24 hours.
>
> Because of that, users will see the default `Generating screenshot...`
> image instead of the actual screenshot. To avoid that, we should have a
> network-wide cron job that makes non-blocking HTTP requests for each of
> the images every 23 hours, so that they're always available when a user
> needs them.
>
> It should sleep for ~2000 milliseconds between each request to be polite,
> or maybe process them in small batches.
New description:
The plugin uses the mShots service to generate the site screenshots, but
those are built asynchronously when the first request is received, and
then cached for 24 hours.
Because of that, users will see the default `Generating screenshot...`
image instead of the actual screenshot. To avoid that, we should have a
network-wide cron job that makes non-blocking HTTP requests for each of
the images every 23 hours, so that they're always available when a user
needs them.
The requests will need to append `requeue=true` to the URL, to flush the
cached image and generate a new one, resetting the cache expiration.
It should sleep for ~2000 milliseconds between each request to be polite,
or maybe process them in small batches.
--
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1116#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list