3 ms·

That link just says "Use Postgres for caching instead of Redis with UNLOGGED tables". That's not helpful and going one link deeper, it says "reports range from

by NavinF 3y ago

That link just says "Use Postgres for caching instead of Redis with UNLOGGED tables". That's not helpful and going one link deeper, it says "reports range from 10% to more than 90% in speed gain" which is not that fast. > the SO link showing that Postgres cannot do caching (expiring old data) is explicitly addressed Nope, UNLOGGED tables don't expire old data. They just fill up forever unless you use a trigger like the one in the answer I linked. I also don't see anyone claiming they can saturate their network interface with postgres the same way they can with any KV store.

anarazel 3y ago
> I also don't see anyone claiming they can saturate their network interface with postgres the same way they can with any KV store. I recently tested it, and I could trivially saturate a 10GBit interface with postgres. https://news.ycombinator.com/item?id=35296130 https://news.ycombinator.com/item?id=35296130
- NavinF 3y ago
  With concurrent writes?
  - anarazel 3y ago
    I'm sure there's a rate of concurrent writes where that wouldn't be true anymore, but if so, you're likely not going to be benefiting that much from the approach to caching.