Replies: 1 comment
-
This solution has all the same problems of cache invalidation that the linked PRs. For now we've put on hold the idea of caching at this level, and we're trying the see how to improve perf without caching or with more granular caching |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
link to #1309
Evan says: we can dump the in memory transform cache to disk on server close, and "hydrate" the module graph on next server start
i just think: if we can quickly compute every request hash, and use disk cache to save the relation of etag and hash
{
'xx etag': 'xx hash'
}
while restart the server, if a req's hash and etag matched,maybe we can quickly return 304 ,to avoid some slow part of the module processing
similar to #10671
Suggested solution
...
Alternative
No response
Additional context
No response
Validations
Beta Was this translation helpful? Give feedback.
All reactions