- 28 Oct, 2020 1 commit
-
-
filipe oliveira authored
-
- 26 Oct, 2020 1 commit
-
-
filipe oliveira authored
- add test suite coverage for redis-benchmark - add --version (similar to what redis-cli has) - fix bug sending more requests than intended when pipeline > 1. - when done sending requests, avoid freeing client in the write handler, in theory before responses are received (probably dead code since the read handler will call clientDone first) Co-authored-by:
Oran Agra <oran@redislabs.com>
-
- 20 Oct, 2020 1 commit
-
-
filipe oliveira authored
Fixed bug concerning redis-benchmark non clustered benchmark forcing always the same hash tag {tag} (#7931) Adding the ":{tag}" only if --cluster is used, so that when used against a proxy it generates traffic to all shards. Co-authored-by:
Oran Agra <oran@redislabs.com>
-
- 17 Sep, 2020 1 commit
-
-
Wang Yuan authored
Redis 6.0 introduces I/O threads, it is so cool and efficient, we use C11 _Atomic to establish inter-thread synchronization without mutex. But the compiler that must supports C11 _Atomic can compile redis code, that brings a lot of inconvenience since some common platforms can't support by default such as CentOS7, so we want to implement redis atomic type to make it more portable. We have implemented our atomic variable for redis that only has 'relaxed' operations in src/atomicvar.h, so we implement some operations with 'sequentially-consistent', just like the default behavior of C11 _Atomic that can establish inter-thread synchronization. And we replace all uses of C11 _Atomic with redis atomic variable. Our implementation of redis atomic variable uses C11 _Atomic, __atomic or __sync macros if available, it supports most common platforms, and we will detect automatically which feature we use. In Makefile we use a dummy file to detect if the compiler supports C11 _Atomic. Now for gcc, we can compile redis code theoretically if your gcc version is not less than 4.1.2(starts to support __sync_xxx operations). Otherwise, we remove use mutex fallback to implement redis atomic variable for performance and test. You will get compiling errors if your compiler doesn't support all features of above. For cover redis atomic variable tests, we add other CI jobs that build redis on CentOS6 and CentOS7 and workflow daily jobs that run the tests on them. For them, we just install gcc by default in order to cover different compiler versions, gcc is 4.4.7 by default installation on CentOS6 and 4.8.5 on CentOS7. We restore the feature that we can test redis with Helgrind to find data race errors. But you need install Valgrind in the default path configuration firstly before running your tests, since we use macros in helgrind.h to tell Helgrind inter-thread happens-before relationship explicitly for avoiding false positives. Please open an issue on github if you find data race errors relate to this commit. Unrelated: - Fix redefinition of typedef 'RedisModuleUserChangedFunc' For some old version compilers, they will report errors or warnings, if we re-define function type.
-
- 25 Aug, 2020 1 commit
-
-
filipe oliveira authored
A first step to enable a consistent full percentile analysis on query latency so that we can fully understand the performance and stability characteristics of the redis-server system we are measuring. It also improves the instantaneous reported metrics, and the csv output format.
-
- 15 Aug, 2020 1 commit
-
-
michael-grunder authored
-
- 11 Aug, 2020 1 commit
-
-
zhaozhao.zz authored
-
- 08 Aug, 2020 1 commit
-
-
ShooterIT authored
-
- 06 Aug, 2020 1 commit
-
-
ShooterIT authored
-
- 10 Jul, 2020 1 commit
-
-
马永泽 authored
Co-authored-by: Oran Agra <oran@redislabs.com> (styling)
-
- 19 May, 2020 1 commit
-
-
hwware authored
-
- 18 May, 2020 1 commit
-
-
ShooterIT authored
The function of generating random data is designed by antirez. See #7196.
-
- 05 May, 2020 1 commit
-
-
ShooterIT authored
-
- 04 May, 2020 1 commit
-
-
Benjamin Sergeant authored
-
- 22 Jul, 2019 1 commit
-
-
antirez authored
This is extremely useful in order to simulate an high load of requests about different keys, and force Redis to track a lot of informations about several clients, to simulate real world workloads.
-
- 05 Jun, 2019 1 commit
-
-
artix authored
-
- 26 Apr, 2019 2 commits
-
-
vattezhang authored
-
vattezhang authored
-
- 24 Apr, 2019 1 commit
-
-
git-hulk authored
-
- 08 Apr, 2019 1 commit
-
-
antirez authored
-
- 13 Mar, 2019 1 commit
-
-
vattezhang authored
-
- 12 Mar, 2019 1 commit
-
-
artix authored
Fixes issue #5912
-
- 08 Mar, 2019 1 commit
-
-
artix authored
-
- 07 Mar, 2019 2 commits
- 01 Mar, 2019 12 commits
-
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
- MOVED or ASK replies are now handled in cluster mode. - Only the first slot per node is used in cluster mode. - Mutlithreading: reduced usage of mutexes in favor of atomic vars.
-
artix authored
-
artix authored
-
artix authored
-
- 26 Feb, 2019 1 commit
-
-
Madelyn Olson authored
-
- 18 Feb, 2019 1 commit
-
-
vattezhang authored
When we run benchmark but forget to set the right requirepass, benchmark should return error.
-
- 14 Feb, 2019 1 commit
-
-
antirez authored
Reltaed to discussion and PR #5840.
-