Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache prefilling #22

Open
PEM-- opened this issue Feb 15, 2017 · 1 comment
Open

Cache prefilling #22

PEM-- opened this issue Feb 15, 2017 · 1 comment
Milestone

Comments

@PEM--
Copy link
Member

PEM-- commented Feb 15, 2017

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.

@PEM-- PEM-- added this to the 3.0.0 milestone Feb 15, 2017
@cbilotta
Copy link
Member

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants