783859 - Kuma editor: With a primed cache, more than 6 seconds to check that we don't need to reload plugins

Status: RESOLVED WORKSFORME

(developer.mozilla.org Graveyard :: Editing, defect, P3)

Description

[Jean-Yves Perrier [:teoli]]

Even with an adequate cache, CKEditor checks for the dozen or so plugins it uses (this is normal!). Even if all these requests lead to a 304 NOT MODIFIED, it still use about 6s to get the answer! This is not normal.

That explains a good deal of the 20s I need to load an $edit page, with a primed cache (25-30s with an empty cache).

To prevent this, we need to set the Expires: and Cache-control: HTTP headers far in the future for CKEditor files.

The good news is that CKEditor is revved (it has a ?t=C6HH5UF at the end), so we really only need to set the headers far in the future (1y, 10y, …). A change in CKEditor will lead to new URLs.

Very likely (but to be checked) these headers has to be added on all files on this directory and its subdirectories (recursively):
https://developer.mozilla.org/media/ckeditor/

This alone may speed a good 20-30% the load of $edit page with a primed cache.

This bug would help a lot heavy editors! I've estimated that I'm spending about 10 min each day waiting the editor to load.

Comment 1

[Jean-Yves Perrier [:teoli]]

This has been fixed at the same time we introduced our CDN :-)