You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once the cache is invalidated, the next HTML payload generation can hit server performances badly. By analysing the sitemaps and when the server is under used, we trigger a queue of routes to re-render prefilling the cache.
The text was updated successfully, but these errors were encountered:
Do we build a hook for people to generate the caches by their own means or do we make our own queue, etc.. ?
Sometimes I use some packages to manage a job queue, threads etc... So I could just use that to do the cache pre-filling when I feel it is more appropriate for my apps.
If we include that in the package, that might be redundant with apps packages, and potentially make optimizations problems, no ?
Or, we make the "api" for cache pre-filling, then we do a separate package that plugs into it if the user doesn't want to manage it himself ?
That way a user could even have the flexibility to offload cache pre-filling to another server, etc...
Once the cache is invalidated, the next HTML payload generation can hit server performances badly. By analysing the sitemaps and when the server is under used, we trigger a queue of routes to re-render prefilling the cache.
The text was updated successfully, but these errors were encountered: