Closed tve closed 1 year ago
Personally I would recommend using the nutsdb setup, badger has been nothing but unstable for myself. (I am also caching pretty big full page responses).
In the latest version redis support has also been added which may be an even better option. Caddy caching in general is still pretty flakey but its definitely getting better with the latest releases.
Hi @tve can you retry with the latest version please?
I also had this issue with the latest master
commit and traced it down to: https://github.com/dgraph-io/badger/issues/60
@jpds same as explained here https://github.com/caddyserver/cache-handler/issues/55#issuecomment-1638919674
I'm trying to cache a 2.7MB response and I get a badger error (see #8):
Looks like there's a 1MB limit. The README points to "See the Badger configuration for the options" which links to https://dgraph.io/docs/badger/get-started/. Well, I'm probably blind, but I don't see any documentation about configuration there.
I'm also not finding any information on how the cache handler uses badger (store metadata, store responses, store ...?). Nor on what the default configuration is. E.g. is it used as in-memory cache, or on disk? If the latter, where is the data stored on disk? ...
I tried the following, but it doesn't change the error:
Putting the badger config in the global cache directive has the same results.