- 16 Jun, 2017 1 commit
-
-
Aric Huang authored
Fix a few typos/adjust wording in `create-cluster` README
-
- 14 Apr, 2017 1 commit
-
-
antirez authored
-
- 09 Mar, 2017 1 commit
-
-
antirez authored
-
- 16 Dec, 2016 1 commit
-
-
antirez authored
The PFADD now takes an array and has mandatory two arguments.
-
- 28 Jul, 2016 1 commit
-
-
antirez authored
-
- 20 Jul, 2016 1 commit
-
-
antirez authored
-
- 14 Jul, 2016 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
We have 24 total bits of space in each object in order to implement an LFU (Least Frequently Used) eviction policy. We split the 24 bits into two fields: 8 bits 16 bits +--------+----------------+ | LOG_C | Last decr time | +--------+----------------+ LOG_C is a logarithmic counter that provides an indication of the access frequency. However this field must also be deceremented otherwise what used to be a frequently accessed key in the past, will remain ranked like that forever, while we want the algorithm to adapt to access pattern changes. So the remaining 16 bits are used in order to store the "decrement time", a reduced-precision unix time (we take 16 bits of the time converted in minutes since we don't care about wrapping around) where the LOG_C counter is halved if it has an high value, or just decremented if it has a low value. New keys don't start at zero, in order to have the ability to collect some accesses before being trashed away, so they start at COUNTER_INIT_VAL. The logaritmic increment performed on LOG_C takes care of COUNTER_INIT_VAL when incrementing the key, so that keys starting at COUNTER_INIT_VAL (or having a smaller value) have a very high chance of being incremented on access. The simulation starts with a power-law access pattern, and later converts into a flat access pattern in order to see how the algorithm adapts. Currenty the decrement operation period is 1 minute, however note that it is not guaranteed that each key will be scanned 1 time every minute, so the actual frequency can be lower. However under high load, we access 3/5 keys every newly inserted key (because of how Redis eviction works). This is a work in progress at this point to evaluate if this works well.
-
- 11 Jul, 2016 2 commits
-
-
antirez authored
-
antirez authored
1. Scan keys with pause to account for actual LRU precision. 2. Test cross-DB with 100 keys allocated in DB1. 3. Output results that don't fluctuate depending on number of keys. 4. Output results in percentage to make more sense. 5. Save file instead of outputting to STDOUT. 6. Support running multiple times with average of outputs. 7. Label each square (DIV) with its ID as HTML title.
-
- 01 Jul, 2016 1 commit
-
-
antirez authored
-
- 10 Jun, 2016 1 commit
-
-
Michiel De Mey authored
-
- 13 May, 2016 1 commit
-
-
Michiel De Mey authored
This PR adds the ability to execute the installation script non-interactively, useful for automated provisioning scripts such as Chef, Puppet, Ansible, Salt, etc. Simply feed the environment variables into the install script to skip the prompts. For debug and verification purposes, the script will still output the selected config variables. The plus side is that the environment variables also support command substitution (see REDIS_EXECUTABLE). ``` sudo REDIS_PORT=1234 REDIS_CONFIG_FILE=/etc/redis/1234.conf REDIS_LOG_FILE=/var/log/redis_1234.log REDIS_DATA_DIR=/var/lib/redis/1234 REDIS_EXECUTABLE=`command -v redis-server` ./utils/install_server.sh Welcome to the redis service installer This script will help you easily set up a running redis server Selected config: Port : 1234 Config file : /etc/redis/1234.conf Log file : /var/log/redis_1234.log Data dir : /var/lib/redis/1234 Executable : /usr/local/bin/redis-server Cli Executable : /usr/local/bin/redis-cli Copied /tmp/1234.conf => /etc/init.d/redis_1234 Installing service... Successfully added to chkconfig! Successfully added to runlevels 345! Starting Redis server... Installation successful! ```
-
- 04 May, 2016 1 commit
-
-
antirez authored
Sometimes Redis patch releases are released in a matter of weeks or days one after the other. In order to have less release friction the idea is to stop writing changelogs by hand, in order to also cover everything interesting there is to say. Useless things can be deleted manually by the changelog. Also this gives more credits to contributors since often in the commit message involved people are cited even when they are not the authors of the commit.
-
- 28 Jan, 2016 1 commit
-
-
antirez authored
-
- 20 Nov, 2015 1 commit
-
-
antirez authored
Used to generate http://antirez.com/news/98.
-
- 17 Nov, 2015 1 commit
-
-
antirez authored
-
- 05 May, 2015 1 commit
-
-
antirez authored
-
- 23 Mar, 2015 1 commit
-
-
superlogical authored
-
- 13 Mar, 2015 1 commit
-
-
antirez authored
-
- 25 Feb, 2015 1 commit
-
-
antirez authored
-
- 18 Feb, 2015 1 commit
-
-
Sisir Koppaka authored
-
- 11 Feb, 2015 1 commit
-
-
antirez authored
-
- 03 Feb, 2015 1 commit
-
-
antirez authored
-
- 30 Jan, 2015 2 commits
- 29 Jan, 2015 1 commit
-
-
antirez authored
-
- 28 Jan, 2015 1 commit
-
-
antirez authored
Simple shell script to create / destroy Redis clusters for manual testing.
-
- 09 Dec, 2014 1 commit
-
-
antirez authored
-
- 05 Dec, 2014 2 commits
-
-
Serghei Iakovlev authored
Improved getting pid
-
Serghei Iakovlev authored
```sh $ ~ pidof redis-server # nothing $ ~ ps aux | grep [r]edis redis 593 0.0 0.0 36900 5564 ? Ssl Dec02 1:37 /usr/bin/redis-server 127.0.0.1:6379 klay 15927 0.0 0.0 16772 6068 pts/6 S+ 13:58 0:00 redis-cli $ ~ uname -a Linux edge 3.17.4-1-ARCH #1 SMP PREEMPT Fri Nov 21 21:14:42 CET 2014 x86_64 GNU/Linux ```
-
- 26 Oct, 2014 1 commit
-
-
Ben Dowling authored
status command currently reports success when redis has crashed and the pid file still exists. Changing to check the actual process is running.
-
- 09 Oct, 2014 1 commit
-
-
antirez authored
-
- 29 Sep, 2014 1 commit
-
-
Aniruddh Chaturvedi authored
Closes #2005
-
- 19 Sep, 2014 4 commits