The first number is the mm:ss when the full dataset was cached.
The second number is the mm:ss when the car was cached.
Because the full dataset is cached for 1h, we expect the first number to never change, while the second number should change every 60s.
---
What we actually observe:
$ rm -rf .next/cache/ && npm run build && npm run start
✅ The page is loaded with all cache times matching current time.
✅ Refreshing the page doesn't change the cache times.
✅ After 60 seconds, the ID cache times change.
❌ After 60 seconds, the full dataset cache times remain the same. The time for the full dataset changed.
❌ After 60 seconds, we do not observe the getAllCars log in the console. We observe 3 such logs.
✅ After pressing the revalidate IDs button, the ID cache times change.
❌ After pressing the revalidate IDs button, the full dataset cache times remain the same.
✅ After pressing the revalidate dataset button, the full dataset cache times remain the same. Because the time comes from the L1 ID cache, which is not revalidated.
✅ After pressing the revalidate dataset button, the ID cache times remain the same.Because the time comes from the L1 ID cache, which is not revalidated.