Disable LRU cache
#21535
Replies: 3 comments 1 reply
-
|
Proposed a solution in PR #27337 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Another solution was proposed in PR #27335 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
What is the actual purpose of this in-memory Incremental Cache? Could someone explain? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
We now know it keeps track of what urls have resulted in 404's and redirects. When this memory runs out on larger sites, previously deleted pages magically reappear: |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I'm looking into serving the static files/doing ISSG while using CDN's cache and would like to disable the LRU cache that is set in next-server completely. That cache object sets the data for the pages when the revalidation happens, and I would like to avoid that and instead use the file system as the source of truth.
Is it possible?
Refs:
https://github.com/vercel/next.js/blob/canary/packages/next/next-server/server/incremental-cache.ts
https://github.com/vercel/next.js/blob/canary/packages/next/next-server/server/next-server.ts#L264
https://github.com/vercel/next.js/blob/canary/packages/next/next-server/server/next-server.ts#L1758
Beta Was this translation helpful? Give feedback.
All reactions