4 ms·
I would note that these rows have almost no content in them. In my experience, your cache entries are usually gonna be a ton of pre-serialized bytes or some js
by forrest2 5y ago
I would note that these rows have almost no content in them.
In my experience, your cache entries are usually gonna be a ton of pre-serialized bytes or some json blobs -- which could be on the order of kbs or mbs. That'll be where redis/memcached start to really shine.
- weird-eye-issue 5y agoI was thinking the same. If you have wide rows in Postgres then read performance will drop quickly. Of course if you can keep it in cache then that is great but for a mixed workload you aren't likely to see a hot cache all the time