Re^2: Big cache -- CHI Unified cache handling interface

Replies are listed 'Best First'.
Re^3: Big cache -- CHI Unified cache handling interface by hippo (Archbishop) on Jul 29, 2022 at 12:38 UTC
Yes, I do use it quite a bit. It presents a uniform interface to a variety of back-ends and so essentially performs the same function for caching as DBI does for databases. My testing of it has shown negligible overhead for my use cases but of course every user should do their own benchmarking just in case. If you use caching at all then I thoroughly recommend CHI. 🦛	[reply]
Re^4: Big cache -- CHI Unified cache handling interface by Anonymous Monk on Dec 25, 2022 at 14:18 UTC
Unfortunately, it's basically unmaintained. The author has been MIA since 2015. Not only are bug reports ignored, but patches/pull requests are also ignored.	[reply]
Re^5: Big cache -- CHI Unified cache handling interface by hippo (Archbishop) on Dec 26, 2022 at 12:34 UTC
The author has been MIA since 2015. So it would seem. swartz hasn't been seen here since 2012 and his domain has been snaffled by a drop-catcher. Fortunately the co-maintainers are still around and there was a release last year. However, this does look like something which needs fixing, so hopefully this useful module will receive a bit more attention going forward. 🦛	[reply]
Re^6: Big cache -- CHI Unified cache handling interface by choroba (Cardinal) on Dec 27, 2022 at 00:37 UTC
Re^7: Big cache -- CHI Unified cache handling interface by hippo (Archbishop) on Dec 27, 2022 at 10:51 UTC
Some notes below your chosen depth have not been shown here
Re^6: Big cache -- CHI Unified cache handling interface by Anonymous Monk on Dec 26, 2022 at 16:12 UTC
Re^3: Big cache -- CHI Unified cache handling interface by 1nickt (Canon) on Jul 29, 2022 at 12:44 UTC
Disci+ I also use CHI a lot; note that there is a Dancer/Dancer2 plugin where you can use CHI as your cache layer and swap out back ends by just changing the config of the app. Thus you can have the same code for test env and production, and just specify the actual cache engine in the relvant config, e.g. in memory for testing and a DB for production. Hope this helps! The way forward always starts with a minimal test.	[reply]