We have an experimental proof-of-concept site up live now (partial content exposure only) that we are using to test the combination of this module LiteSpeed Cache, and the Redis module (https://www.drupal.org/project/redis).

Our frankly, nutty proposal is that we can actually build a good publicly-available educational community website for use by trainee Computer Science teachers using only very low-cost shared hosting and some very nifty caching and cache-warming.

Well, let's see how that goes ;-)

Anyway, we are all up for some testing scenarios under the direction of the module maintainers if that's be useful.

Here are some heavy composite pages hopefully getting to you at 'lite speed'... ?

https://bit-by-bit.org/node/6811
https://bit-by-bit.org/tutorials/computer-science
https://bit-by-bit.org/tutorials/binary-numbers
https://bit-by-bit.org/statements
https://bit-by-bit.org/test-yourself

Comments

sirclickalot created an issue. See original summary.

sirclickalot’s picture

sirclickalot
Primary language English
Location Somerset
commented
Title: Available for » Available for testing RC1
dinis’s picture

dinis commented

Glad you're up for testing, thanks, it's much appreciated.

1.3.0-rc1 is the right cut. It's the cumulative current release (public cache from 1.0.x, private cache for authenticated users from 1.1.x, ESI for mixed pages from 1.2.x, vary cookies from 1.3.x), and the URLs you listed (tutorial pages, the test-yourself page) all look like the anonymous-cacheable shape that 1.0.x's public-cache mode was designed for. Public cache is the only feature on by default; the rest are opt-in via the settings form.

For the Redis-stacking part of the picture, your other thread (#3589109) has the request-lifecycle walkthrough. Short version: Redis sits below PHP, LSCache sits in front of PHP, the two stack rather than compete.

A few things worth watching as the install settles in:

  • `curl -sI https://bit-by-bit.org/tutorials/computer-science` should show `x-litespeed-cache: hit` on the second consecutive request (first will be miss). If you see `X-LiteSpeed-Tag` and `X-LiteSpeed-Cache-Control` headers but no `x-litespeed-cache:` header at all, the `.htaccess` setup isn't right and the Status report row will flag what's missing.
  • Tag invalidation: edit a tutorial node, immediately re-fetch its URL, confirm you don't get a stale response. If you see stale persisting past edits, the Purge submodule's `purge_host` config probably needs attention.
  • Any 5xx or unexpected PHP errors after the upgrade. The admin-route skip in 1.1+ was field-tested on a separate site but each LSWS environment can surface different patterns.

If you enable private-cache mode (1.1.x) for authenticated content, the `.htaccess` directive changes from `CacheLookup public on` to `CacheLookup public on private on`. The Status report row will flag this. ESI (1.2.x) and vary cookies (1.3.x) are opt-in if you have a use case, otherwise leave them off.

Two weeks of clean operation under normal traffic is the signal that justifies cutting 1.3.0 stable, though, to be honest, I'm kinda impatient and will probably rush it through. Anything you find during the window is useful, particularly the "looks like caching but isn't" kind of surprise. Reply here as you go, or open separate issues for anything bug-shaped.

sirclickalot’s picture

sirclickalot
Primary language English
Location Somerset
commented

What's happened here,1.3x has suddenly disappeared, we were just getting started ;-)

Ah, looking through the various releases, I can see we've rolled back to beta.

dinis’s picture

dinis commented

Yeah, found a critical error and squashed it. I rushed it out too quickly. New release soon.