antirez weblog - comments http://antirez.com antirez weblog - comments it-it Giuseppe Ciuni su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1549 http://antirez.com/post/203#c1549 Ciao totò, ti ho scritto un messaggio su gtalk. Spero che tu lo legga. Ciao Giuseppe Ciuni 2010-03-10T14:24:38+00:00 Navigatore Anonimo su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1548 http://antirez.com/post/203#c1548 2010-03-10T14:23:56+00:00 mimi holliday su Asus EEE PC, not just a little and cheap laptop http://antirez.com/post/177#c1547 http://antirez.com/post/177#c1547 A dream come true for the people who want cheap laptop with the big portability, It support wifi stimulated my dreams about this little computers that were almost as easy to carry around as cellular phones but much more usable, with a fairly big screen and a real keyboard. 2010-03-09T10:48:59+00:00 mimi holliday su Antenna monodirezionale per wifi con "affare" per cottura a vapore http://antirez.com/post/110#c1546 http://antirez.com/post/110#c1546 Nice post and thanks for your information on Unidirectional antenna for wifi with "bargain" for steaming 2010-03-09T10:38:55+00:00 Axeryon su Una grande fetta di informatici non e' in grado di programmare? http://antirez.com/post/44#c1545 http://antirez.com/post/44#c1545 St4alk3r la tua versione non stampa il numero se nessuna delle condizioni è vera :) Ecco la mia versione :-D #include <iostream> int main() { for (int i = 1; i <= 100; i++) if (i % 3 == 0 && i % 5 == 0) std::cout << "FizzBuzz" << std::endl; else if (i % 3 == 0) std::cout << "Fizz" << std::endl; else if (i % 5 == 0) std::cout << "Buzz" << std::endl; else std::cout << i << std::endl; return 0; } 2010-02-26T21:28:43+00:00 Joe su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1544 http://antirez.com/post/203#c1544 Is there a way to get the 160 bytes per key down? My actual keys are on average 15 bytes and the value is only 1 byte. I have over 100 million records but using 16GB just for the keys is a killer. currently using multiple cdb files. 2010-02-26T18:58:15+00:00 t3kwhat su Attacker: SUCA http://antirez.com/post/106#c1543 http://antirez.com/post/106#c1543 SUCA! quasi ogni volta che sono su internet e non so cosa fare scrivo "suca" su google e oggi, scrivendo "suca google" ho trovato questo splendido post che si intreccia su due piani, uno mega nerd riguardo un problema di protezione e uno parallelo riguardo alla parola, secondo me, più bella della lingua italiana. Suca può voler dire tutto. Suca! Son quattro lettere." quoto---- 2010-02-25T05:04:12+00:00 antirez su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1542 http://antirez.com/post/203#c1542 @Ashwin: a very big part of the article is about why this can't be used for Redis ;) 2010-02-24T21:29:05+00:00 Ashwin Jayaprakash su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1541 http://antirez.com/post/203#c1541 I may have misunderstood your explanation (very likely) but I thought I saw some similarities between your "VM" implementation and the problems explained here - http://varnish-cache.org/wiki/ArchitectNotes#Sowhatswrongwith1975programming 2010-02-24T21:17:10+00:00 jimmybot su MongoDB and Redis: a different interpretation of what's wrong with Relational DBs http://antirez.com/post/195#c1540 http://antirez.com/post/195#c1540 Wow you are fast. Thanks. I think you are right that SQL can be unpredictable, though *if* there was some kind of index on value functionality, it could be implemented in a way with predictable performance. At any rate, Redis looks to be shaping up very interestingly. Props on a great project. 2010-02-19T20:50:35+00:00 antirez su MongoDB and Redis: a different interpretation of what's wrong with Relational DBs http://antirez.com/post/195#c1539 http://antirez.com/post/195#c1539 @jimmybot: ah ok, got it, indeed it is true. In Redis you have to build all your "views" by hand. But this also means you don't have surprises. Most SQL troubles come from the fact you ask queries that are processed inside a black box. With Redis you have to handle more carefully your model, but you end up with something really predictable. 2010-02-19T20:31:42+00:00 jimmybot su MongoDB and Redis: a different interpretation of what's wrong with Relational DBs http://antirez.com/post/195#c1538 http://antirez.com/post/195#c1538 Well, I mean you can just store the value as a key and the key as a value, but I think it's one more thing to think about and possibly get wrong. 2010-02-19T20:29:40+00:00 antirez su MongoDB and Redis: a different interpretation of what's wrong with Relational DBs http://antirez.com/post/195#c1537 http://antirez.com/post/195#c1537 @jimmybot: search Redis "Sorted Sets". It's our Index. 2010-02-19T20:24:45+00:00 jimmybot su MongoDB and Redis: a different interpretation of what's wrong with Relational DBs http://antirez.com/post/195#c1536 http://antirez.com/post/195#c1536 My understanding of redis is that there is no built-in easy index for <i>values</i>. No index means slow queries/searches. I think that is a very big difference as well, though not something that can't be changed. 2010-02-19T20:23:22+00:00 lucie su Antenna monodirezionale per wifi con "affare" per cottura a vapore http://antirez.com/post/110#c1531 http://antirez.com/post/110#c1531 una yagi antenna wifi è molto meglio! http://www.frequence-wifi.com 2010-02-08T17:12:49+00:00 Dhruv su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1530 http://antirez.com/post/203#c1530 @antirez: Nice, resque looks good :) 2010-02-05T04:26:11+00:00 Demis Bellot su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1529 http://antirez.com/post/203#c1529 Awesome work again antirez! - You are quickly eliminating any reasons for not using Redis. It is already the most versatile key-value store around and the best technology I've seen yet to come out of the NO-SQL movement. Keep up the good work! 2010-02-04T15:38:15+00:00 antirez su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1528 http://antirez.com/post/203#c1528 @Dhruv: Resque! :) http://github.com/blog/542-introducing-resque Also check this: http://github.com/gleicon/restmq It is one of the top use cases for Redis. 2010-02-04T15:16:58+00:00 Dhruv su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1527 http://antirez.com/post/203#c1527 Actually, I am looking to use redis for a persistence store for a message queue. Do you know if there is anyone using it in that way? 2010-02-04T15:09:26+00:00 antirez su Redis Virtual Memory: the story and the code http://antirez.com/post/203#c1526 http://antirez.com/post/203#c1526 @chh: Redis already does it for integers. With strings it's also trivial but for now I'm not doing it as most of the strings are small enough to be impossible to compress with standard algorithms (so I developed one btw, called smaz, you can find more in my github page). When writing on disk we can compress much more for a reason: we lose the structure of data. A list or a set all become just a simple string consisting of elements with a separator. So there in memory it's not possible to compress the same way as you need the right connections and organization of data in order to ensure the expected time complexity. @Dhruv: yes I see how there are good and bad things about the two different approaches, I just think that everything considered the user-land VM is the best compromise, at least for Redis. But for other kind of applications the best can be exactly the reverse, to build a vertical allocator or even simpler just using the OS paging, and I think this is the first approach to try. When there are no alternatives there is to implement an user-land VM that is indeed more complex but has its big advantages. 2010-02-04T13:56:53+00:00