-
Notifications
You must be signed in to change notification settings - Fork 744
FAQs
- Python 2.6, 2.7, 3.4, and 3.5 are officially supported. We have tests in place to ensure ongoing support.
- Mark Costello added support for Python 2.5 in his redis-rdb-tools clone. If you need python 2.5 support, please add a comment to Issue#25.
All Versions. We have unit tests for versions 2 through 6. If you happen to have a version 1 dump file, please upload it to a new issue, and I will gladly add unit tests for it as well.
The dump file stores the unix time in milliseconds precision. This does not have the timezone information. The parser converts this unix time into UTC. Your local clock may or may not be running UTC, and hence the difference.
If you know the timezone used while saving records in redis, you can always convert the UTC time back to the correct timezone.
The memory reported by this tool is approximate. In general, the reported memory should be within 10% of what is reported by info
Also note that the tool does not (and cannot) account for the following -
- Memory used by client buffers
- Memory used for pub/sub
- Redis process overheads
- Export redis into a relational database like MySQL
- Export redis into a full text search engine like solr or amazon cloud search, so that you can do (almost) real time, full text search.
- Merge or split dump files. This is useful if you using several instances of Redis and shard your data
- Build a UI/Explorer for the data in Redis
- Build a tool that recommends changes that would reduce memory usage. The tool can recommend appropriate values for settings in redis.conf. It can also detect small strings that should instead be stored in a hash. Several other interesting possibilities exist.
Yes.
- redis-rdb is written in Ruby
- rdbhs is written in Haskell
- rdb-parser is written in Node.js
- rdb is written in Go
You should directly contact the respective authors in case you have questions.
You can always create a parser for your language of choice. The dump file specification is straightforward. The parser code is contained in a single file - parser.py, so it should be easy to port.
You can reuse the test dump files to test your parser implementation. parser_tests.py uses these dump files to ensure the parser is working properly. You can use these tests as a starting point for your parser implementation.