- 10 May, 2019 9 commits
-
-
Salvatore Sanfilippo authored
Makefile: 1TD -> STD
-
Salvatore Sanfilippo authored
Preserve client->id for blocked clients.
-
Salvatore Sanfilippo authored
change the comments there may have a mis type
-
Salvatore Sanfilippo authored
delete sdsTest() from REDIS_TEST in server.c to fix build failed
-
Salvatore Sanfilippo authored
fix-inappropriate-add-operation-code
-
Salvatore Sanfilippo authored
Fix uint64_t hash value in active defrag
-
Salvatore Sanfilippo authored
[Minor] Fix build warnings on Linux
-
Salvatore Sanfilippo authored
test cases: skiptill -> skip-till
-
zhaozhao.zz authored
-
- 08 May, 2019 4 commits
-
-
Angus Pearson authored
Enlarge error buffer in redis-check-aof.c to remove compiler warning of output truncation through snprintf format string
-
Angus Pearson authored
-
yongman authored
-
唐权 authored
Hi, @antirez In the code, to get the size of ziplist, "unsigned int bytes = ZIPLIST_HEADER_SIZE+1;" is correct, but why not make it more readable and easy to understand
-
- 07 May, 2019 4 commits
-
-
Salvatore Sanfilippo authored
fix memory leak when rewrite config file
-
zhaozhao.zz authored
-
stan011 authored
-
zhaozhao.zz authored
-
- 06 May, 2019 21 commits
-
-
Salvatore Sanfilippo authored
make replication tests more stable on slow machines
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Potentially it is possible that we get interleaved writes, even if serverLog() makes sure to write into a buffer and then use printf(), so even this should be ok. However in general POSIX guarantees that writing to the same file pointer object from multiple threads is safe. Anyway currently we *reopen* the file at each call, but for the standard output logging. The logging functions actually also access global configuration while performing the log (for instance in order to check the log level, the log filename and so forth), however dunring the I/O threads execution we cannot alter such shared state in any way.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
Ubuntu authored
Now threads are stopped even when the connections drop immediately to zero, not allowing the networking code to detect the condition and stop the threads. serverCron() will handle that.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This is just an experiment for now, there are a couple of race conditions, mostly harmless for the performance gain experiment that this commit represents so far. The general idea here is to take Redis single threaded and instead fan-out on expansive kernel calls: write(2) in this case, but the same concept could be easily implemented for read(2) and protcol parsing. However just threading writes like in this commit, is enough to evaluate if the approach is sounding.
-
liaotonglang authored
sdsTest() defined in sds.c dit not match the call in server.c. remove it from REDIS_TEST, since test-sds defined in Makefile.
-
- 05 May, 2019 2 commits
-
-
Yossi Gottlieb authored
-
Oran Agra authored
solving few replication related tests race conditions which fail on slow machines bugfix in slave buffers test: since the test is executed twice, each time with a different commands count, the threshold for the delta can't be a constant.
-