- Issue created by @ambient.impact
At the time of writing, Turbo only stores its cache in memory and not in any persistent storage, so reloads completely wipe out its cache. Additionally, Turbo seems to limit the number of cached snapshots it keeps in memory - for good reason - which means that preloading links (see 📌 Add a lazy link preloader to warm Turbo and Drupal caches while scrolling Active ) is even more likely to result in wasted data transfer.
Do a full load after a bunch of stuff is preloaded, note how it needs to send requests to preload the same things again. Also note how older links may need to be fetched again during the same Turbo session.
It looks like they tried and then reverted a pull request to add support for the Cache API. It sounds like it was mostly working but had some issues, and that they do intend to merge it in again once they can fix the issues they encountered. It may be worth trying it to see if we're affected by any of the issues they encountered, because if not, then we would instantly have persistent caching.
Patch Turbo and test it out.
Cached snapshots displayed more.
Probably none.
None.
Active
2.0
Code