Earlier quoted context omitted.
Is this satire? "man" here is short for "manual".
Manual? What if someone lacks hands? It's not a manual. It's a reference guide.
[deleted]
Redis 4.0
81–90 of 184 posts
Re: Redis 4.0
#82Re: Redis 4.0
#83@antirez: Congrats! Are you going to modularize disque now that v4 is ready?
Yes, one of the top items in the Redis 4.2 roadmap is to port Disque as a Redis module, so the steps are: 1) Implement a Redis Cluster modules API (I've already some draft design, basically there are low level stuff to enlist nodes, broadcast messages, send one-to-one messages, and have callbacks called when we receive a message), and then port Disque as Redis module on top of such API, so that we can both validate t…
I'm very excited about this!
Re: Redis 4.0
#84"9) Active memory defragmentation. Redis is able to defragment the memory while online..." I'm so amazed that this is a thing.
Memory fragmentation is largely related to the allocator you're using (ie: glibc malloc, jemalloc, tcmalloc) and previously it was up to the OS to manage this (ie: freeing up unused memory). Now with active memory defragmentation things are a bit more pleasant, specifically with high delete load actually freeing up unused memory in a timely manner without impacting performance too much. Previously, to fully recover u…
120GB on a single thread, yeah.
Redis has been abused for quite some time but 120GB is way out of reasonable reach for current CPU arch if you use a single core only (even if you switch off hyper threading)
Re: Redis 4.0
#85Earlier quoted context omitted.
"Slave" is technically incorrect. There are better terms to describe the behavior such as "follower" or "replica". If someone has been around long enough to understand what a "slave" is can't figure out what a "replica" or a "follower" does, maybe they shouldn't be in tech. The transition cost for documentation is essentially zero. Naming things is hard, and better names are better for everyone. Antirez said he would…
I agree that the terminology doesn't matter, but consensus does. Master/slave are the commonly understood terms. Here's a question: if "slave" is offensive, should "kill" (as in 'kill 69' to kill a process in SQL Server) be considered offensive as well? Simply as a consequence of being something 'bad/immoral'? I'm sorry, and I'd be glad to be corrected, but I genuinely find this argument...disingenuous. And people wh…
Master/slave was also a commonly accepted role of business for far longer than it has been a computer term. We managed to change that in the west. I believe in us, we can do it.
> I genuinely find this argument...disingenuous
My argument is that the term is not technically correct. How is that disingenuous?
Re: Redis 4.0
#86Earlier quoted context omitted.
Except in nearly every case, this is the reality of the situation: http://i.imgur.com/erINvSI.png It isn't that the people are offended - it's that others are trying to get offended "on their behalf" as a form of virtue signalling. Also see most of the "cultural appropriation" movement. Where non-Japanese people get offended that other non-Japanese wear kimono while nearly every actual Japanese person I've seen on th…
> Almost every individual I see calling to "fix" this issue is a white person speaking on "behalf" of black people. Could it be that black people are put off by people fighting for their right to use words that have no significance for them, but need to remain just "on principle", and that they're put off by such behaviour, avoid the tech sector, and therefore aren't there to be visibly offended whenever you're looki…
It's common well outside the tech sector. My (black) ex frequently complains how white people try to speak on black peoples behalf about what should offend her, for example.
To the point that she more than once have been in rage over white people accusing her (to her face) of being offensive to black people for saying something that they just assumed black people in general should find offensive.
She's also part of the diversity board of a major bank, where she sits on a panel that is mostly old white men talking about what issues affects their minorities and women, without a hint of recognition from any of them of the irony in that they've not recruited more minority representatives and women from their staff to be on the board itself.
Re: Redis 4.0
#87Earlier quoted context omitted.
Arguing for not offending others by saying to someone that they seem to lack empathy is gutsy.
I'm not opposed to offending others. : ) Just be aware when you do, and why you're doing it. The parent post simply seemed blithely unaware of how deeply hurtful the phrase can be to people. (Imagine typing that phrase out every day when literally your own great great great grandparents were dragged here in chains and were considered the personal property of someone. That's simply f'ed up and would suck beyond belief…
Honest question: Is that how you feel when you type those out?
Re: Redis 4.0
#88Earlier quoted context omitted.
> I'm getting quite fed up of the OTT political correctness movement in tech. Is it over the top though? It's a references to a deplorable practice that humans do; why shouldn't we strive for something more civil, and more technically correct? The slave of a database isn't the property of the master and subject to its every whim; it's a replica of the data that can do separate, independent things from the master with…
> deplorable actions humans do. So when do we rename 'kill'?
...or killall
Re: Redis 4.0
#89Earlier quoted context omitted.
"Slave" is technically incorrect. There are better terms to describe the behavior such as "follower" or "replica". If someone has been around long enough to understand what a "slave" is can't figure out what a "replica" or a "follower" does, maybe they shouldn't be in tech. The transition cost for documentation is essentially zero. Naming things is hard, and better names are better for everyone. Antirez said he would…
It's not just a replica, it can work offline for a while and push back. Leader/follower is also flawed in my opinion. It's master and a slave even if it offends your sensibilities. These arguments are a waste of everyone's time. >This hill you're dying on looks awfully lonely. Ironic coming from a grey response to a 15 point comment. I will change my tune if even one victim of slavery comes forward and speaks about t…
> It's not just a replica, it can work offline for a while and push back. Leader/follower is also flawed in my opinion. It's master and a slave even if it offends your sensibilities.
I'm glad that your concerned that "follower" and "replica" aren't perfect terms. We should be concerned with terminology.
I humbly suggest that "slave" DBs are not physically whipped by their "masters", therefore are an even worse metaphor.
> These arguments are a waste of everyone's time.
Then why are you wasting your time? If you don't care, don't argue back. Boom, you've got your time back. We all get a better name, everyone is happy.
Re: Redis 4.0
#90"9) Active memory defragmentation. Redis is able to defragment the memory while online..." I'm so amazed that this is a thing.
It is one of those things where people say "Java can be faster than C/C++ because it can compact memory" and the C/C++ lady says "here, hold my beer"
To be fair only a compacting GC can do that