@@ -29,12 +29,13 @@ The following libraries are required for building:
29
29
The following tools are required
30
30
* autoconf
31
31
* automake
32
+ * pkg-config
32
33
* GNU make
33
34
* GCC C++ compiler
34
35
35
- ### CentOS 6.x Prerequisites
36
+ #### CentOS 6.x
36
37
37
- On a CentOS 6.4 system, use the following to install prerequisites:
38
+ On a CentOS 6.x system, use the following to install prerequisites:
38
39
```
39
40
# yum install autoconf automake make gcc-c++
40
41
# yum install pcre-devel zlib-devel libmemcached-devel
@@ -64,33 +65,21 @@ $ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:${PKG_CONFIG_PATH}
64
65
65
66
Then proceed to follow the build instructions below.
66
67
68
+ #### Ubuntu/Debian
67
69
68
- ### Ubuntu 12.x Prerequisites
69
-
70
- On recent Ubuntu versions, simply install all prerequisites as follows:
70
+ On Ubuntu/Debian distributions, simply install all prerequisites as follows:
71
71
72
72
```
73
73
# apt-get install build-essential autoconf automake libpcre3-dev libevent-dev pkg-config zlib1g-dev
74
74
```
75
75
76
+ #### macOS
76
77
77
- ### Cluster mode
78
-
79
- #### Connections
80
-
81
- When using the cluster-mode option, each client opens one connection for each node.
82
- So, when using a large number of threads and clients, the user must verify that he is not
83
- limited by the maximum number of file descriptors.
84
-
85
- #### Using sequential key pattern
86
-
87
- When there is an asymmetry between the Redis nodes and user set
88
- the --requests option, there may be gaps in the generated keys.
89
-
90
- Also, the ratio and the key generator is per client (and not connection).
91
- In this case, setting the ratio to 1:1 does not guarantee 100% hits because
92
- the keys spread to different connections/nodes.
78
+ To build natively on macOS, use Homebrew to install the required dependencies::
93
79
80
+ ```
81
+ $ brew install autoconf automake libtool libevent pkg-config
82
+ ```
94
83
95
84
### Building and installing
96
85
@@ -121,5 +110,24 @@ $ memtier_benchmark --help
121
110
for command line options.
122
111
123
112
113
+ ### Cluster mode
114
+
115
+ #### Connections
116
+
117
+ When using the cluster-mode option, each client opens one connection for each node.
118
+ So, when using a large number of threads and clients, the user must verify that he is not
119
+ limited by the maximum number of file descriptors.
120
+
121
+ #### Using sequential key pattern
122
+
123
+ When there is an asymmetry between the Redis nodes and user set
124
+ the --requests option, there may be gaps in the generated keys.
125
+
126
+ Also, the ratio and the key generator is per client (and not connection).
127
+ In this case, setting the ratio to 1:1 does not guarantee 100% hits because
128
+ the keys spread to different connections/nodes.
129
+
130
+
131
+
124
132
125
133
[ ![ githalytics.com alpha] ( https://cruel-carlota.pagodabox.com/c1e8ecf15c469fbeb0e4eb12e8436c82 " githalytics.com ")] ( http://githalytics.com/RedisLabs/memtier_benchmark )
0 commit comments