15:19:16 GMT <elfranne> when running redis-cli --bigkeys i do get info about the number of item in a key ... how can i get that info about a key ?
15:19:41 GMT <elfranne> DEBUG OBJECT did not give me number of item in a key
15:36:55 GMT <badboy_> elfranne: depends on the type behind the key
15:37:50 GMT <elfranne> i tried most of them them and found out that LLEN did the job
15:38:38 GMT <elfranne> just started using Redis, IRC is so good
15:46:01 GMT <badboy_> LLEN works for lists
15:46:06 GMT <badboy_> you can get the type with TYPE <key>
15:52:27 GMT <elfranne> that will be usefull thx
16:20:22 GMT <Stummi> Hi, I am quite new to redis and not sure if redis is the best fit for my use case, so I hope someone can give a hint. I want to have a set of entities, indexed by name, containing two string lists as properties. Heres a simplified example of what my structure looks like: https://gist.github.com/Stummi/767a16f2c42a188a2fab2d90da21053f
16:20:59 GMT <Stummi> I want to lookup them by name, and search by content of the lists, like "all entities which have "b" in produces"
16:22:03 GMT <sembiance> Stummi: do the lists contain unique values? or unique items.
16:22:20 GMT <Stummi> unique per list, yes. But two entities can produce or consume the same thing
16:24:04 GMT <sembiance> Stummi: well, redis has the "SET" type. https://redis.io/commands#set   So you could create a key like this:   SADD foo_consumes a b c   SADD foo_produces d e    and if you wanted to see if "b" is in foo_consumes you would do   SISMEMBER foo_consumes b
16:27:30 GMT <sembiance> Stummi: the more general question, as to whether or not to use redis depends on a few factors. Redis is CRAZY FAST, but also is really best with all data in RAM. So if you have a TON of data, you may not want to use redis as you'll need RAM to store it all. Also, being in RAM, if the server loses power or something, you'll lose whatever was in RAM since the last time you had redis save the data to disk (unless you change how redis operates by defa
16:29:42 GMT <sembiance> Stummi: I myself use redis for my web game. It stores user info such as preferences and game statistics. My redis instance uses 45GB of RAM and I have it save to disk twice a day as I don't care too much if I lose up to 12 hours of data (although in multiple years of running, never ran into a server crash or power outage or anything yet)
16:30:11 GMT <sembiance> Stummi: also note that I've never doing anything with redis cluster and several people have databases much larger than mine
16:30:37 GMT <Stummi> well, my db would be kinda small, maybe holding a few MB of data
16:32:31 GMT <sembiance> so that's no problem then :)
16:35:28 GMT <sembiance> stummi: back when I was getting started, I found it most useful to write down all the different types of data my app/site needed to store. I then looked at the different redis data types (https://redis.io/topics/data-types-intro) and thought about which ones would work with my different data. Then I would just experiment and try things out :)
16:36:00 GMT <sembiance> stummi: I am a developer of 1 though, nobody else needed access to this data and I knew my usage of it was going to be pretty straightforward and wasn't likely to change drastically in the future
16:37:00 GMT <Stummi> yeah, I know this site. I somehow miss more complex structures, like maps with lists as values and so on :)
16:39:35 GMT <sembiance> I myself, LOVE redis. It's one of the coolest techs I've come across in the past decade or so. I would look to it as my DB of choice for almost every single future project, so long as it makes sense. I just love it's blazingly fast speeds and data types :)
19:13:16 GMT <zautomata> is it possible send syslog msgs to redis?
20:01:50 GMT <zpojqwfejwfhiunz> zautomata: yeah, all things are possible with Redis