Dion Hulse 2:08 am on April 4, 2022
Tags: cache ( 3 ), codex ( 7 ), prio2 ( 100 )

Clear codex cache & lower cache TTL?

Per https://meta.trac.wordpress.org/ticket/6168 some codex pages have a cached header HTML + CSS which are incompatible with one another, causing a display mismatch.

While we’re migrating away from the Codex, it appears likely to remain for some time.

Can we please
1. Flush the codex cache
2. Lower the cache TTL, perhaps to a week or two, to avoid the need for future system requests?

#codex #cache #prio2

abbe 4:18 am on May 5, 2022

Flush the codex cache

Done.

Lower the cache TTL, perhaps to a week or two, to avoid the need for future system requests?

I don’t see any obvious way in Mediawiki to do this. Do you know of any ?
- Dion Hulse 2:49 am on May 12, 2022
  
  Lower the cache TTL, perhaps to a week or two, to avoid the need for future system requests?
  
  I don’t see any obvious way in Mediawiki to do this. Do you know of any ?
  
  I had assumed there would be one, but upon reading the docs closer, I see there isn’t an explicit cache-ttl option, only a setting to invalidate all cached pages.
  
  It seems they encourage the usage of webserver level caching instead for more complicated scenario’s.
  
  Systems call on this, I can see several options, and I’m fine with any of them:
  1. Do nothing, leave it as-is. Make requests when needed.
  2. Cron job which deletes any cache files older than x days.
  3. MediaWiki extension that allows sysop mediawiki users to invalidate the entire cache from a special auth’d page.
  
  I can’t find an existing extension for the last one, so it’d have to be a custom extension (which I’m happy to look into). If you’d be interested in this, to remove the need for sysreq’s, LMK.
  
  Thanks for looking at this @762e5e74!
  - Barry 11:02 pm on May 12, 2022
    
    I think we can just switch to NginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. caching and set the TTL to something like 24 hours? Do you still need manual cache invalidation in that case?
    
    Systems note: To do this, we need to modfy some Mediawiki config to set the proper caching headers
    
    https://www.mediawiki.org/wiki/Manual:$wgUseCdn
    https://www.mediawiki.org/wiki/Manual:$wgCdnMaxAge
    - Dion Hulse 3:12 am on June 17, 2022
      
      I think we can just switch to NginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. caching and set the TTL to something like 24 hours? Do you still need manual cache invalidation in that case?
      
      Nginx would be perfect. No manual cache invalidation needed in that case IMHO – We’ll just tell editors that it’s heavily cached and will clear tomorrow.
      
      Cache bypass for logged in users will probably suffice as we do elsewhere on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ on the wporg_loggged_in cookie, but the codex also sets codex_session for authenticated users.