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
What is the problem your feature solves, or the need it fulfills?
Looks like pingora already provides a memory-cache module, but I suspect memory caching may be cost prohibitive for a lot of folks currently using something like NGINX, which caches to disk by default.
Describe the solution you'd like
Would be great to see a disk-cache module in addition to the memory-cache module!
Describe alternatives you've considered
We could always implement custom disk caching modules in user-land since pingora is so extensible, and the fact that the current memory-cache module is already abstracted behind a generic interface probably makes this even easier. But having off-the-shelf disk-caching would make it a lot easier to migrate existing NGINX-based workloads and help accelerate adoption.
Additional context
The fact that there's no disk-cache module in pingora makes me super curious about how Cloudflare handling caching with pingora today. Is all caching done in-memory (sounds expensive!)? Or maybe you have dedicated disk caching services living outside of the pingora proxies themselves? Would love to learn more. May be a good blog post topic? :)
The text was updated successfully, but these errors were encountered:
What is the problem your feature solves, or the need it fulfills?
Looks like pingora already provides a memory-cache module, but I suspect memory caching may be cost prohibitive for a lot of folks currently using something like NGINX, which caches to disk by default.
Describe the solution you'd like
Would be great to see a disk-cache module in addition to the memory-cache module!
Describe alternatives you've considered
We could always implement custom disk caching modules in user-land since pingora is so extensible, and the fact that the current memory-cache module is already abstracted behind a generic interface probably makes this even easier. But having off-the-shelf disk-caching would make it a lot easier to migrate existing NGINX-based workloads and help accelerate adoption.
Additional context
The fact that there's no disk-cache module in pingora makes me super curious about how Cloudflare handling caching with pingora today. Is all caching done in-memory (sounds expensive!)? Or maybe you have dedicated disk caching services living outside of the pingora proxies themselves? Would love to learn more. May be a good blog post topic? :)
The text was updated successfully, but these errors were encountered: