21–30 of 56 posts
Questions I would like to see answered: - How does oss redis compare to enterprise redis ? - What are the differences when running the same benchmarks with both oss redis and enterprise redis ? - what is the marginal utility of an additional cpu core/thread ? that is, what happens if I run those benchmarks on an AMD ThreadRipper ?
Questions I would like to see answered: - How does oss redis compare to enterprise redis ? - What are the differences when running the same benchmarks with both oss redis and enterprise redis ? - what is the marginal utility of an additional cpu core/thread ? that is, what happens if I run those benchmarks on an AMD ThreadRipper ?
I'm curious on all of these as well. Also, is this a first party (ie antirez) piece of software? If not, has he blessed calling something "Redis Enterprise"?
Questions I would like to see answered: - How does oss redis compare to enterprise redis ? - What are the differences when running the same benchmarks with both oss redis and enterprise redis ? - what is the marginal utility of an additional cpu core/thread ? that is, what happens if I run those benchmarks on an AMD ThreadRipper ?
I'm curious on all of these as well. Also, is this a first party (ie antirez) piece of software? If not, has he blessed calling something "Redis Enterprise"?
Very impressive, especially how it doesn't seem to matter much on the read/write ratio. I've only used redis to cache, do folks really use it as a DB?
Some of it was done with raw Redis commands, and for some we wrote a data-store engine with automatic indexing and optional mapping to models - https://github.com/EverythingMe/meduza
We also used Redis for geo tagging, queuing, caching, and other stuff I forgot probably. It is very flexible, but requires some effort when not used as just a cache.
Right now I'm developing a module for Redis 4.0 that can do full-text and general purpose secondary indexing in Redis. https://github.com/RedisLabsModules/RediSearch
Earlier quoted context omitted.
I'm curious on all of these as well. Also, is this a first party (ie antirez) piece of software? If not, has he blessed calling something "Redis Enterprise"?
I believe he still works for redislabs, so I'm sure this is all done with his knowledge.
Questions I would like to see answered: - How does oss redis compare to enterprise redis ? - What are the differences when running the same benchmarks with both oss redis and enterprise redis ? - what is the marginal utility of an additional cpu core/thread ? that is, what happens if I run those benchmarks on an AMD ThreadRipper ?
Re the second and third questions - I'm afraid I cannot answer. I hope the author of the post will reply tomorrow morning (it's the middle of the night here).
I don't like to admit but I still don't get it, could I use Redis as a main webapp backend?
Very impressive, especially how it doesn't seem to matter much on the read/write ratio. I've only used redis to cache, do folks really use it as a DB?
I'd also like to know what else is it used for.
In general, an extra layer on top of Redis is a must to make it even simple searchable database. Especially indices can't be ad-hoc implemented with separate Redis commands. Only transactions or Lua snippets that update both data and related indices atomically can avoid data corruption. For my own use, I wrote: https://github.com/ilkkao/rigidDB It supports indices and strict schema for the data.
I think somebody has described Redis at some point as a database-SDK. Makes sense to me.
I don't like to admit but I still don't get it, could I use Redis as a main webapp backend?
Redis won't function till it has loaded all data from disk to memory. So if your webapp doesn't have too much data then possibly. Also since Redis is memory backed you need more RAM then data. This can get very costly. Another annoyance is that Redis is single process single threaded so you really have to avoid running long running queries unless you do extensive manual sharding. (Disclaimer: it's been a few years si…