-FAQ: Contents
Why I need Redis if there is already memcachedb, Tokyo Cabinet, ...?
Isn't this key-value thing just hype?
Can I backup a Redis DB while the server is working?
What's the Redis memory footprint?
I like Redis high level operations and features, but I don't like it takes everything in memory and I can't have a dataset larger the memory. Plans to change this?
Ok but I absolutely need to have a DB larger than memory, still I need the Redis features
I have an empty Redis server but INFO and logs are reporting megabytes of memory in use!
What happens if Redis runs out of memory?
How much time it takes to load a big database at server startup?
What Redis means actually?
Why did you started the Redis project? +FAQ: Contents
Why I need Redis if there is already memcachedb, Tokyo Cabinet, ...?
Isn't this key-value thing just hype?
Can I backup a Redis DB while the server is working?
What's the Redis memory footprint?
I like Redis high level operations and features, but I don't like it takes everything in memory and I can't have a dataset larger the memory. Plans to change this?
Ok but I absolutely need to have a DB larger than memory, still I need the Redis features
I have an empty Redis server but INFO and logs are reporting megabytes of memory in use!
What happens if Redis runs out of memory?
How much time it takes to load a big database at server startup?
Redis is single threaded, how can I exploit multiple CPU / cores?
I'm using some form of key hashing for partitioning, but what about SORT BY?
What is the maximum number of keys a single Redis instance can hold?
What Redis means actually?
Why did you started the Redis project?
Why I need Redis if there is already memcachedb, Tokyo Cabinet, ...?
Isn't this key-value thing just hype?
Can I backup a Redis DB while the server is working?
What's the Redis memory footprint?
I like Redis high level operations and features, but I don't like it takes everything in memory and I can't have a dataset larger the memory. Plans to change this?
Ok but I absolutely need to have a DB larger than memory, still I need the Redis features
I have an empty Redis server but INFO and logs are reporting megabytes of memory in use!
What happens if Redis runs out of memory?
How much time it takes to load a big database at server startup?
What Redis means actually?
Why did you started the Redis project? +FAQ: Contents
Why I need Redis if there is already memcachedb, Tokyo Cabinet, ...?
Isn't this key-value thing just hype?
Can I backup a Redis DB while the server is working?
What's the Redis memory footprint?
I like Redis high level operations and features, but I don't like it takes everything in memory and I can't have a dataset larger the memory. Plans to change this?
Ok but I absolutely need to have a DB larger than memory, still I need the Redis features
I have an empty Redis server but INFO and logs are reporting megabytes of memory in use!
What happens if Redis runs out of memory?
How much time it takes to load a big database at server startup?
Redis is single threaded, how can I exploit multiple CPU / cores?
I'm using some form of key hashing for partitioning, but what about SORT BY?
What is the maximum number of keys a single Redis instance can hold?
What Redis means actually?
Why did you started the Redis project?
FAQ
@@ -34,7 +34,7 @@ So Redis offers more features:- Keys can store different data t
- We wrote a simple Twitter Clone using just Redis as database. Download the source code from the download section and imagine to write it with a plain key-value DB without support for lists and sets... it's much harder.
- Multiple DBs. Using the SELECT command the client can select different datasets. This is useful because Redis provides a MOVE atomic primitive that moves a key form a DB to another one, if the target DB already contains such a key it returns an error: this basically means a way to perform locking in distributed processing.
- So what is Redis really about? The User interface with the programmer. Redis aims to export to the programmer the right tools to model a wide range of problems. Sets, Lists with O(1) push operation, lrange and ltrim, server-side fast intersection between sets, are primitives that allow to model complex problems with a key value database.
Isn't this key-value thing just hype?
I imagine key-value DBs, in the short term future, to be used like you use memory in a program, with lists, hashes, and so on. With Redis it's like this, but this special kind of memory containing your data structures is shared, atomic, persistent.
When we write code it is obvious, when we take data in memory, to use the most sensible data structure for the work, right? Incredibly when data is put inside a relational DB this is no longer true, and we create an absurd data model even if our need is to put data and get this data back in the same order we put it inside (an ORDER BY is required when the data should be already sorted. Strange, dont' you think?).
Key-value DBs bring this back at home, to create sensible data models and use the right data structures for the problem we are trying to solve.Can I backup a Redis DB while the server is working?
Yes you can. When Redis saves the DB it actually creates a temp file, then rename(2) that temp file name to the destination file name. So even while the server is working it is safe to save the database file just with the cp unix command. Note that you can use master-slave replication in order to have redundancy of data, but if all you need is backups, cp or scp will do the work pretty well.What's the Redis memory footprint?
Worst case scenario: 1 Million keys with the key being the natural numbers from 0 to 999999 and the string "Hello World" as value use 100MB on my Intel macbook (32bit). Note that the same data stored linearly in an unique string takes something like 16MB, this is the norm because with small keys and values there is a lot of overhead. Memcached will perform similarly.
With large keys/values the ratio is much better of course.
64 bit systems will use much more memory than 32 bit systems to store the same keys, especially if the keys and values are small, this is because pointers takes 8 bytes in 64 bit systems. But of course the advantage is that you can have a lot of memory in 64 bit systems, so to run large Redis servers a 64 bit system is more or less required.I like Redis high level operations and features, but I don't like it takes everything in memory and I can't have a dataset larger the memory. Plans to change this?
The whole key-value hype started for a reason: performances. Redis takes the whole dataset in memory and writes asynchronously on disk in order to be very fast, you have the best of both worlds: hyper-speed and persistence of data, but the price to pay is exactly this, that the dataset must fit on your computers RAM.
If the data is larger then memory, and this data is stored on disk, what happens is that the bottleneck of the disk I/O speed will start to ruin the performances. Maybe not in benchmarks, but once you have real load from multiple clients with distributed key accesses the data must come from disk, and the disk is damn slow. Not only, but Redis supports higher level data structures than the plain values. To implement this things on disk is even slower.
Redis will always continue to hold the whole dataset in memory because this days scalability requires to use RAM as storage media, and RAM is getting cheaper and cheaper. Today it is common for an entry level server to have 16 GB of RAM! And in the 64-bit era there are no longer limits to the amount of RAM you can have in theory.Ok but I absolutely need to have a DB larger than memory, still I need the Redis features
You may try to load a dataset larger than your memory in Redis and see what happens, basically if you are using a modern Operating System, and you have a lot of data in the DB that is rarely accessed, the OS's virtual memory implementation will try to swap rarely used pages of memory on the disk, to only recall this pages when they are needed. If you have many large values rarely used this will work. If your DB is big because you have tons of little values accessed at random without a specific pattern this will not work (at low level a page is usually 4096 bytes, and you can have different keys/values stored at a single page. The OS can't swap this page on disk if there are even few keys used frequently).
Another possible solution is to use both MySQL and Redis at the same time, basically take the state on Redis, and all the things that get accessed very frequently: user auth tokens, Redis Lists with chronologically ordered IDs of the last N-comments, N-posts, and so on. Then use MySQL as a simple storage engine for larger data, that is just create a table with an auto-incrementing ID as primary key and a large BLOB field as data field. Access MySQL data only by primary key (the ID). The application will run the high traffic queries against Redis but when there is to take the big data will ask MySQL for specific resources IDs.I have an empty Redis server but INFO and logs are reporting megabytes of memory in use!
This may happen and it's prefectly ok. Redis objects are small C structures allocated and freed a lot of times. This costs a lot of CPU so instead of being freed, released objects are taken into a free list and reused when needed. This memory is taken exactly by this free objects ready to be reused.What happens if Redis runs out of memory?
With modern operating systems malloc() returning NULL is not common, usually the server will start swapping and Redis performances will be disastrous so you'll know it's time to use more Redis servers or get more RAM.
However it is planned to add a configuration directive to tell Redis to stop accepting queries but instead to SAVE the latest data and quit if it is using more than a given amount of memory. Also the new INFO command (work in progress in this days) will report the amount of memory Redis is using so you can write scripts that monitor your Redis servers checking for critical conditions.
Update: redis SVN is able to know how much memory it is using and report it via the INFO command.How much time it takes to load a big database at server startup?
Just an example on normal hardware: It takes about 45 seconds to restore a 2 GB database on a fairly standard system, no RAID. This can give you some kind of feeling about the order of magnitude of the time needed to load data when you restart the server.What Redis means actually?
Redis means two things: +Isn't this key-value thing just hype?
I imagine key-value DBs, in the short term future, to be used like you use memory in a program, with lists, hashes, and so on. With Redis it's like this, but this special kind of memory containing your data structures is shared, atomic, persistent.
When we write code it is obvious, when we take data in memory, to use the most sensible data structure for the work, right? Incredibly when data is put inside a relational DB this is no longer true, and we create an absurd data model even if our need is to put data and get this data back in the same order we put it inside (an ORDER BY is required when the data should be already sorted. Strange, dont' you think?).
Key-value DBs bring this back at home, to create sensible data models and use the right data structures for the problem we are trying to solve.Can I backup a Redis DB while the server is working?
Yes you can. When Redis saves the DB it actually creates a temp file, then rename(2) that temp file name to the destination file name. So even while the server is working it is safe to save the database file just with the cp unix command. Note that you can use master-slave replication in order to have redundancy of data, but if all you need is backups, cp or scp will do the work pretty well.What's the Redis memory footprint?
Worst case scenario: 1 Million keys with the key being the natural numbers from 0 to 999999 and the string "Hello World" as value use 100MB on my Intel macbook (32bit). Note that the same data stored linearly in an unique string takes something like 16MB, this is the norm because with small keys and values there is a lot of overhead. Memcached will perform similarly.
With large keys/values the ratio is much better of course.
64 bit systems will use much more memory than 32 bit systems to store the same keys, especially if the keys and values are small, this is because pointers takes 8 bytes in 64 bit systems. But of course the advantage is that you can have a lot of memory in 64 bit systems, so to run large Redis servers a 64 bit system is more or less required.I like Redis high level operations and features, but I don't like it takes everything in memory and I can't have a dataset larger the memory. Plans to change this?
The whole key-value hype started for a reason: performances. Redis takes the whole dataset in memory and writes asynchronously on disk in order to be very fast, you have the best of both worlds: hyper-speed and persistence of data, but the price to pay is exactly this, that the dataset must fit on your computers RAM.
If the data is larger then memory, and this data is stored on disk, what happens is that the bottleneck of the disk I/O speed will start to ruin the performances. Maybe not in benchmarks, but once you have real load from multiple clients with distributed key accesses the data must come from disk, and the disk is damn slow. Not only, but Redis supports higher level data structures than the plain values. To implement this things on disk is even slower.
Redis will always continue to hold the whole dataset in memory because this days scalability requires to use RAM as storage media, and RAM is getting cheaper and cheaper. Today it is common for an entry level server to have 16 GB of RAM! And in the 64-bit era there are no longer limits to the amount of RAM you can have in theory.Ok but I absolutely need to have a DB larger than memory, still I need the Redis features
You may try to load a dataset larger than your memory in Redis and see what happens, basically if you are using a modern Operating System, and you have a lot of data in the DB that is rarely accessed, the OS's virtual memory implementation will try to swap rarely used pages of memory on the disk, to only recall this pages when they are needed. If you have many large values rarely used this will work. If your DB is big because you have tons of little values accessed at random without a specific pattern this will not work (at low level a page is usually 4096 bytes, and you can have different keys/values stored at a single page. The OS can't swap this page on disk if there are even few keys used frequently).
Another possible solution is to use both MySQL and Redis at the same time, basically take the state on Redis, and all the things that get accessed very frequently: user auth tokens, Redis Lists with chronologically ordered IDs of the last N-comments, N-posts, and so on. Then use MySQL as a simple storage engine for larger data, that is just create a table with an auto-incrementing ID as primary key and a large BLOB field as data field. Access MySQL data only by primary key (the ID). The application will run the high traffic queries against Redis but when there is to take the big data will ask MySQL for specific resources IDs.I have an empty Redis server but INFO and logs are reporting megabytes of memory in use!
This may happen and it's prefectly ok. Redis objects are small C structures allocated and freed a lot of times. This costs a lot of CPU so instead of being freed, released objects are taken into a free list and reused when needed. This memory is taken exactly by this free objects ready to be reused.What happens if Redis runs out of memory?
With modern operating systems malloc() returning NULL is not common, usually the server will start swapping and Redis performances will be disastrous so you'll know it's time to use more Redis servers or get more RAM.
However it is planned to add a configuration directive to tell Redis to stop accepting queries but instead to SAVE the latest data and quit if it is using more than a given amount of memory. Also the new INFO command (work in progress in this days) will report the amount of memory Redis is using so you can write scripts that monitor your Redis servers checking for critical conditions.
Update: redis SVN is able to know how much memory it is using and report it via the INFO command.How much time it takes to load a big database at server startup?
Just an example on normal hardware: It takes about 45 seconds to restore a 2 GB database on a fairly standard system, no RAID. This can give you some kind of feeling about the order of magnitude of the time needed to load data when you restart the server.Redis is single threaded, how can I exploit multiple CPU / cores?
Simply start multiple instances of Redis in different ports in the same box and threat them as different servers! Given that Redis is a distributed database anyway in order to scale you need to think in terms of multiple computational units. At some point a single box may not be enough anyway.
In general key-value databases are very scalable because of the property that different keys can stay on different servers independently.
In Redis there are client libraries such Redis-rb (the Ruby client) that are able to handle multiple servers automatically using consistent hashing. We are going to implement consistent hashing in all the other major client libraries. If you use a different language you can implement it yourself otherwise just hash the key before to SET / GET it from a given server. For example imagine to have N Redis servers, server-0, server-1, ..., server-N. You want to store the key "foo", what's the right server where to put "foo" in order to distribute keys evenly among different servers? Just perform the crc = CRC32("foo"), then servernum = crc % N (the rest of the division for N). This will give a number between 0 and N-1 for every key. Connect to this server and store the key. The same for gets.
This is a basic way of performing key partitioning, consistent hashing is much better and this is why after Redis 1.0 will be released we'll try to implement this in every widely used client library starting from Python and PHP (Ruby already implements this support).I'm using some form of key hashing for partitioning, but what about SORT BY?
With SORT BY you need that all the weight keys are in the same Redis instance of the list/set you are trying to sort. In order to make this possible we developed a concept called key tags. A key tag is a special pattern inside a key that, if preset, is the only part of the key hashed in order to select the server for this key. For example in order to hash the key "foo" I simply perform the CRC32 checksum of the whole string, but if this key has a pattern in the form of the characters {...} I only hash this substring. So for example for the key "foo{bared}" the key hashing code will simply perform the CRC32 of "bared". This way using key tags you can ensure that related keys will be stored on the same Redis instance just using the same key tag for all this keys. Redis-rb already implements key tags.What is the maximum number of keys a single Redis instance can hold?
The latest versions of Redis in the Git repository are able to handle at least 150 million of keys per instance. We are working in order to experiment with larger values.What Redis means actually?
Redis means two things:- it's a joke on the word Redistribute (instead to use just a Relational DB redistribute your workload among Redis servers)
- it means REmote DIctionary Server
Why did you started the Redis project?
In order to scale LLOOGG. But after I got the basic server working I liked the idea to share the work with other guys, and Redis was turned into an open source project. diff --git a/doc/ReplicationHowto.html b/doc/ReplicationHowto.html new file mode 100644 index 00000000..e3e23499 --- /dev/null +++ b/doc/ReplicationHowto.html @@ -0,0 +1,41 @@ + + + + + + + ++ ++ + + diff --git a/doc/SmoveCommand.html b/doc/SmoveCommand.html index 9c9c54e4..5cbde97e 100644 --- a/doc/SmoveCommand.html +++ b/doc/SmoveCommand.html @@ -28,7 +28,7 @@+ ++ +
+
+ +++ +ReplicationHowto: Contents+ +
Redis Replication Howto
General Information
How Redis replication works
Configuration +ReplicationHowto
+ ++ ++ +++ +Redis Replication Howto
General Information
Redis replication is a very simple to use and configure master-slave replication that allows slave Redis servers to be exact copies of master servers. The following are some very important facts about Redis replication:- A master can have multiple slaves.
- Slaves are able to accept other slaves connections, so instead to connect a number of slaves against the same master it is also possible to connect some of the slaves to other slaves in a graph-alike structure.
- Redis replication is non-blocking on the master side, this means that the master will continue to serve queries while one or more slaves are performing the first synchronization. Instead replication is blocking on the slave side: while the slave is performing the first synchronization it can't reply to queries.
- Replications can be used both for scalability, in order to have multiple slaves for read-only queries (for example heavy SORT operations can be launched against slaves), or simply for data redundancy.
- It is possible to use replication to avoid the saving process on the master side: just configure your master redis.conf in order to avoid saving at all (just comment al the "save" directives), then connect a slave configured to save from time to time.
How Redis replication works
In order to start the replication, or after the connection closes in order resynchronize with the master, the client connects to the master and issues the SYNC command.
The master starts a background saving, and at the same time starts to collect all the new commands received that had the effect to modify the dataset. When the background saving completed the master starts the transfer of the database file to the slave, that saves it on disk, and then load it in memory. At this point the master starts to send all the accumulated commands, and all the new commands received from clients, that had the effect of a dataset modification.
You can try it yourself via telnet. Connect to the Redis port while the server is doing some work and issue the SYNC command. You'll see a bulk transfer and then every command received by the master will be re-issued in the telnet session.
Slaves are able to automatically reconnect when the master<->slave link goes down for some reason. If the master receives multiple concurrent slave synchronization requests it performs a single background saving in order to serve all them.Configuration
To configure replication is trivial: just add the following line to the slave configuration file: ++slaveof 192.168.1.1 6379 +
+Of course you need to replace 192.168.1.1 6379 with your master ip address (or hostname) and port. +SMOVE _srckey_ _dstkey_ _member_
Time complexity O(1)Move the specifided member from the set at srckey to the set at dstkey.This operation is atomic, in every given moment the element will appear tobe in the source or destination set for accessing clients.
-If the source set does not exist or does not contain the specified elementno operation is performed and zero is returned, otherwise the element isremoved from the source set and added to the destination set. On successone is returned, even if the element was already present in the destionationset.
+If the source set does not exist or does not contain the specified elementno operation is performed and zero is returned, otherwise the element isremoved from the source set and added to the destination set. On successone is returned, even if the element was already present in the destinationset.
An error is raised if the source or destination keys contain a non Set value.
Return value
Integer reply, specifically:1 if the element was moved diff --git a/doc/index.html b/doc/index.html index 0b040564..0489b34a 100644 --- a/doc/index.html +++ b/doc/index.html @@ -26,7 +26,7 @@-Redis Documentation
Hello! The followings are pointers to different parts of the Redis Documentation.- The README is the best starting point to know more about the project.
- The command reference is a description of all the Redis commands with links to command specific pages.
- The Protocol Specification is all you need in order to implement a Redis client library for a missing language. PHP, Python, Ruby and Erlang are already supported.
- This is a tuturial about creating a Twitter clone using *only* Redis as database, no relational DB at all is used, it is a good start to understand the key-value database paradigm.
- Our FAQ contains of course some answers to common questions about Redis.
- The benchmark page is about the speed performances of Redis.
- New! video: watch the Ezra Zygmuntowicz talk about Redis to know the most important Redis ideas in few minutes.
Redis Documentation
Hello! The followings are pointers to different parts of the Redis Documentation.- The README is the best starting point to know more about the project.
- The command reference is a description of all the Redis commands with links to command specific pages.
- The Protocol Specification is all you need in order to implement a Redis client library for a missing language. PHP, Python, Ruby and Erlang are already supported.
- This is a tuturial about creating a Twitter clone using *only* Redis as database, no relational DB at all is used, it is a good start to understand the key-value database paradigm.
- The Redis Replication HOWTO is what you need to read in order to understand how Redis master
<->slave replication works. - Our FAQ contains of course some answers to common questions about Redis.
- The benchmark page is about the speed performances of Redis.
- New! video: watch the Ezra Zygmuntowicz talk about Redis to know the most important Redis ideas in few minutes.