Operations
Pages open in about 60 ms again after publishing
Finding the page by its address, which runs on every visit, went through every page of the language. An index on the path fixed it: one row examined and no disk reads.
Right after a publication, every page of the site went from 70 ms to almost one second. The query that finds the page by its address only had an index on the language, so the database read the content of about a thousand pages on each visit. While that fit in the database memory nobody noticed; after publishing, it no longer did.
The pages table got an index on language and path. The query now examines one row, with no disk reads, and time to first byte dropped to about 60 ms in both test environments. Production has not been measured yet.
In short
- From 0.4–0.9 s to about 60 ms
- One row examined per visit
- Prefix index, because the path is long text
Source: Core · REQ-263 · BATCH-272