1 .TH "MEMASLAP" "1" "May 03, 2012" "1.0.7" "libmemcached"
3 memaslap \- libmemcached Documentation
5 .nr rst2man-indent-level 0
9 level \\n[rst2man-indent-level]
10 level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
17 .\" .rstReportMargin pre:
19 . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
20 . nr rst2man-indent-level +1
21 .\" .rstReportMargin post:
25 .\" indent \\n[an-margin]
26 .\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
27 .nr rst2man-indent-level -1
28 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
29 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
31 .\" Man page generated from reStructeredText.
46 \fBmemaslap\fP is a load generation and benchmark tool for memcached
47 servers. It generates configurable workload such as threads, concurrencies,
48 connections, run time, overwrite, miss rate, key size, value size, get/set
49 proportion, expected throughput, and so on. Furthermore, it also testss data
50 verification, expire\-time verification, UDP, binary protocol, facebook test,
51 replication test, multi\-get and reconnection, etc.
53 Memaslap manages network connections like memcached with
54 libevent. Each thread of memaslap is bound with a CPU core, all
55 the threads don\(aqt communicate with each other, and there are several socket
56 connections in each thread. Each connection keeps key size distribution,
57 value size distribution, and command distribution by itself.
59 You can specify servers via the \fImemslap \-\-servers\fP option or via the
60 environment variable \fI\%MEMCACHED_SERVERS\fP.
63 Memslap is developed to for the following purposes:
65 Manages network connections with libevent asynchronously.
67 Set both TCP and UDP up to use non\-blocking IO.
69 Improves parallelism: higher performance in multi\-threads environments.
71 Improves time efficiency: faster processing speed.
73 Generates key and value more efficiently; key size distribution and value size distribution are configurable.
75 Supports get, multi\-get, and set commands; command distribution is configurable.
77 Supports controllable miss rate and overwrite rate.
79 Supports data and expire\-time verification.
81 Supports dumping statistic information periodically.
83 Supports thousands of TCP connections.
85 Supports binary protocol.
87 Supports facebook test (set with TCP and multi\-get with UDP) and replication test.
89 .SS Effective implementation of network.
91 For memaslap, both TCP and UDP use non\-blocking network IO. All
92 the network events are managed by libevent as memcached. The network module
93 of memaslap is similar to memcached. Libevent can ensure
94 memaslap can handle network very efficiently.
95 .SS Effective implementation of multi\-threads and concurrency
97 Memslap has the similar implementation of multi\-threads to
98 memcached. Memslap creates one or more self\-governed threads;
99 each thread is bound with one CPU core if the system testss setting CPU
102 In addition, each thread has a libevent to manage the events of the network;
103 each thread has one or more self\-governed concurrencies; and each
104 concurrency has one or more socket connections. All the concurrencies don’t
105 communicate with each other even though they are in the same thread.
107 Memslap can create thousands of socket connections, and each
108 concurrency has tens of socket connections. Each concurrency randomly or
109 sequentially selects one socket connection from its socket connection pool
110 to run, so memaslap can ensure each concurrency handles one
111 socket connection at any given time. Users can specify the number of
112 concurrency and socket connections of each concurrency according to their
114 .SS Effective implementation of generating key and value
116 In order to improve time efficiency and space efficiency,
117 memaslap creates a random characters table with 10M characters. All the
118 suffixes of keys and values are generated from this random characters table.
120 Memslap uses the offset in the character table and the length
121 of the string to identify a string. It can save much memory.
122 Each key contains two parts, a prefix and a suffix. The prefix is an
123 uint64_t, 8 bytes. In order to verify the data set before,
124 memaslap need to ensure each key is unique, so it uses the prefix to identify
125 a key. The prefix cannot include illegal characters, such as ‘r’, ‘n’,
126 ‘0’ and ‘ ‘. And memaslap has an algorithm to ensure that.
128 Memslap doesn’t generate all the objects (key\-value pairs) at
129 the beginning. It only generates enough objects to fill the task window
130 (default 10K objects) of each concurrency. Each object has the following
131 basic information, key prefix, key suffix offset in the character table, key
132 length, value offset in the character table, and value length.
134 In the work process, each concurrency sequentially or randomly selects an
135 object from the window to do set operation or get operation. At the same
136 time, each concurrency kicks objects out of its window and adds new object
138 .SS Simple but useful task scheduling
140 Memslap uses libevent to schedule all the concurrencies of
141 threads, and each concurrency schedules tasks based on the local task
142 window. Memslap assumes that if each concurrency keeps the same
143 key distribution, value distribution and commands distribution, from
144 outside, memaslap keeps all the distribution as a whole.
145 Each task window includes a lot of objects, each object stores its basic
146 information, such as key, value, expire time, and so on. At any time, all
147 the objects in the window keep the same and fixed key and value
148 distribution. If an object is overwritten, the value of the object will be
149 updated. Memslap verifies the data or expire\-time according to
150 the object information stored in the task window.
152 Libevent selects which concurrency to handle based on a specific network
153 event. Then the concurrency selects which command (get or set) to operate
154 based on the command distribution. If it needs to kick out an old object and
155 add a new object, in order to keep the same key and value distribution, the
156 new object must have the same key length and value length.
158 If memcached server has two cache layers (memory and SSD), running
159 memaslap with different window sizes can get different cache
160 miss rates. If memaslap adds enough objects into the windows at
161 the beginning, and the cache of memcached cannot store all the objects
162 initialized, then memaslap will get some objects from the second
163 cache layer. It causes the first cache layer to miss. So the user can
164 specify the window size to get the expected miss rate of the first cache
166 .SS Useful implementation of multi\-servers , UDP, TCP, multi\-get and binary protocol
168 Because each thread is self\-governed, memaslap can assign
169 different threads to handle different memcached servers. This is just one of
170 the ways in which memaslap tests multiple servers. The only
171 limitation is that the number of servers cannot be greater than the number
172 of threads. The other way to test multiple servers is for replication
173 test. Each concurrency has one socket connection to each memcached server.
174 For the implementation, memaslap can set some objects to one
175 memcached server, and get these objects from the other servers.
177 By default, Memslap does single get. If the user specifies
178 multi\-get option, memaslap will collect enough get commands and
179 pack and send the commands together.
181 Memslap testss both the ASCII protocol and binary protocol,
182 but it runs on the ASCII protocol by default.
183 Memslap by default runs on the TCP protocol, but it also
184 tests UDP. Because UDP is unreliable, dropped packages and out\-of\-order
185 packages may occur. Memslap creates a memory buffer to handle
186 these problems. Memslap tries to read all the response data of
187 one command from the server and reorders the response data. If some packages
188 get lost, the waiting timeout mechanism can ensure half\-baked packages will
189 be discarded and the next command will be sent.
192 Below are some usage samples:
194 memaslap \-s 127.0.0.1:11211 \-S 5s
196 memaslap \-s 127.0.0.1:11211 \-t 2m \-v 0.2 \-e 0.05 \-b
198 memaslap \-s 127.0.0.1:11211 \-F config \-t 2m \-w 40k \-S 20s \-o 0.2
200 memaslap \-s 127.0.0.1:11211 \-F config \-t 2m \-T 4 \-c 128 \-d 20 \-P 40k
202 memaslap \-s 127.0.0.1:11211 \-F config \-t 2m \-d 50 \-a \-n 40
204 memaslap \-s 127.0.0.1:11211,127.0.0.1:11212 \-F config \-t 2m
206 memaslap \-s 127.0.0.1:11211,127.0.0.1:11212 \-F config \-t 2m \-p 2
208 The user must specify one server at least to run memaslap. The
209 rest of the parameters have default values, as shown below:
211 Thread number = 1 Concurrency = 16
213 Run time = 600 seconds Configuration file = NULL
215 Key size = 64 Value size = 1024
217 Get/set = 9:1 Window size = 10k
219 Execute number = 0 Single get = true
221 Multi\-get = false Number of sockets of each concurrency = 1
223 Reconnect = false Data verification = false
225 Expire\-time verification = false ASCII protocol = true
227 Binary protocol = false Dumping statistic information
231 Overwrite proportion = 0% UDP = false
233 TCP = true Limit throughput = false
235 Facebook test = false Replication test = false
236 .SS Key size, value size and command distribution.
238 All the distributions are read from the configuration file specified by user
239 with “—cfg_cmd” option. If the user does not specify a configuration file,
240 memaslap will run with the default distribution (key size = 64,
241 value size = 1024, get/set = 9:1). For information on how to edit the
242 configuration file, refer to the “Configuration File” section.
244 The minimum key size is 16 bytes; the maximum key size is 250 bytes. The
245 precision of proportion is 0.001. The proportion of distribution will be
246 rounded to 3 decimal places.
248 The minimum value size is 1 bytes; the maximum value size is 1M bytes. The
249 precision of proportion is 0.001. The proportion of distribution will be
250 rounded to 3 decimal places.
251 Currently, memaslap only testss set and get commands. And it
252 testss 100% set and 100% get. For 100% get, it will preset some objects to
254 .SS Multi\-thread and concurrency
256 The high performance of memaslap benefits from the special
257 schedule of thread and concurrency. It’s important to specify the proper
258 number of them. The default number of threads is 1; the default number of
259 concurrency is 16. The user can use “—threads” and “\-\-concurrency” to
260 specify these variables.
262 If the system tests setting CPU affinity and the number of threads
263 specified by the user is greater than 1, memaslap will try to
264 bind each thread to a different CPU core. So if you want to get the best
265 performance memaslap, it is better to specify the number of
266 thread equal to the number of CPU cores. The number of threads specified by
267 the user can also be less or greater than the number of CPU cores. Because
268 of the limitation of implementation, the number of concurrencies could be
269 the multiple of the number of threads.
272 For 8 CPU cores system
277 \-\-threads=2 \-\-concurrency=128
279 \-\-threads=8 \-\-concurrency=128
281 \-\-threads=8 \-\-concurrency=256
283 \-\-threads=12 \-\-concurrency=144
286 For 16 CPU cores system
291 \-\-threads=8 \-\-concurrency=128
293 \-\-threads=16 \-\-concurrency=256
295 \-\-threads=16 \-\-concurrency=512
297 \-\-threads=24 \-\-concurrency=288
299 The memaslap performs very well, when
300 used to test the performance of memcached servers.
301 Most of the time, the bottleneck is the network or
302 the server. If for some reason the user wants to
303 limit the performance of memaslap, there
304 are two ways to do this:
306 Decrease the number of threads and concurrencies.
307 Use the option “\-\-tps” that memaslap
308 provides to limit the throughput. This option allows
309 the user to get the expected throughput. For
310 example, assume that the maximum throughput is 50
311 kops/s for a specific configuration, you can specify
312 the throughput equal to or less than the maximum
313 throughput using “\-\-tps” option.
316 Most of the time, the user does not need to specify the window size. The
317 default window size is 10k. For Schooner Memcached, the user can specify
318 different window sizes to get different cache miss rates based on the test
319 case. Memslap testss cache miss rate between 0% and 100%.
320 If you use this utility to test the performance of Schooner Memcached, you
321 can specify a proper window size to get the expected cache miss rate. The
322 formula for calculating window size is as follows:
324 Assume that the key size is 128 bytes, and the value size is 2048 bytes, and
327 1. Small cache cache_size=1M, 100% cache miss (all data get from SSD).
334 (1). cache miss rate 0%
338 (2). cache miss rate 5%
346 (1). cache miss rate 0%
356 The formula for calculating window size for cache miss rate 0%:
358 cache_size / concurrency / (key_size + value_size) * 0.5
360 The formula for calculating window size for cache miss rate 5%:
362 cache_size / concurrency / (key_size + value_size) * 0.7
365 Memslap testss both data verification and expire\-time
366 verification. The user can use "\-\-verify=" or "\-v" to specify the proportion
367 of data verification. In theory, it testss 100% data verification. The
368 user can use "\-\-exp_verify=" or "\-e" to specify the proportion of
369 expire\-time verification. In theory, it testss 100% expire\-time
370 verification. Specify the "\-\-verbose" options to get more detailed error
373 For example: \-\-exp_verify=0.01 –verify=0.1 , it means that 1% of the objects
374 set with expire\-time, 10% of the objects gotten will be verified. If the
375 objects are gotten, memaslap will verify the expire\-time and
377 .SS multi\-servers and multi\-config
379 Memslap testss multi\-servers based on self\-governed thread.
380 There is a limitation that the number of servers cannot be greater than the
381 number of threads. Memslap assigns one thread to handle one
382 server at least. The user can use the "\-\-servers=" or "\-s" option to specify
387 \-\-servers=10.1.1.1:11211,10.1.1.2:11212,10.1.1.3:11213 \-\-threads=6 \-\-concurrency=36
389 The above command means that there are 6 threads, with each thread having 6
390 concurrencies and that threads 0 and 3 handle server 0 (10.1.1.1); threads 1
391 and 4 handle server 1 (10.1.1.2); and thread 2 and 5 handle server 2
394 All the threads and concurrencies in memaslap are self\-governed.
396 So is memaslap. The user can start up several
397 memaslap instances. The user can run memaslap on different client
398 machines to communicate with the same memcached server at the same. It is
399 recommended that the user start different memaslap on different
400 machines using the same configuration.
401 .SS Run with execute number mode or time mode
403 The default memaslap runs with time mode. The default run time
404 is 10 minutes. If it times out, memaslap will exit. Do not
405 specify both execute number mode and time mode at the same time; just
410 \-\-time=30s (It means the test will run 30 seconds.)
412 \-\-execute_number=100000 (It means that after running 100000 commands, the test will exit.)
413 .SS Dump statistic information periodically.
415 The user can use "\-\-stat_freq=" or "\-S" to specify the frequency.
421 Memslap will dump the statistics of the commands (get and set) at the frequency of every 20
424 For more information on the format of dumping statistic information, refer to “Format of Output” section.
427 The user can use "\-\-division=" or "\-d" to specify multi\-get keys count.
428 Memslap by default does single get with TCP. Memslap also testss data
429 verification and expire\-time verification for multi\-get.
431 Memslap testss multi\-get with both TCP and UDP. Because of
432 the different implementation of the ASCII protocol and binary protocol,
433 there are some differences between the two. For the ASCII protocol,
434 memaslap sends one “multi\-get” to the server once. For the
435 binary protocol, memaslap sends several single get commands
436 together as “multi\-get” to the server.
439 Memslap testss both UDP and TCP. For TCP,
440 memaslap does not reconnect the memcached server if socket connections are
441 lost. If all the socket connections are lost or memcached server crashes,
442 memaslap will exit. If the user specifies the “\-\-reconnect”
443 option when socket connections are lost, it will reconnect them.
445 User can use “\-\-udp” to enable the UDP feature, but UDP comes with some
448 UDP cannot set data more than 1400 bytes.
450 UDP is not testsed by the binary protocol because the binary protocol of
451 memcached does not tests that.
453 UDP doesn’t tests reconnection.
456 Set data with TCP and multi\-get with UDP. Specify the following options:
458 "\-\-facebook \-\-division=50"
460 If you want to create thousands of TCP connections, specify the
462 "\-\-conn_sock=" option.
464 For example: \-\-facebook \-\-division=50 \-\-conn_sock=200
466 The above command means that memaslap will do facebook test,
467 each concurrency has 200 socket TCP connections and one UDP socket.
469 Memslap sets objects with the TCP socket, and multi\-gets 50
470 objects once with the UDP socket.
472 If you specify "\-\-division=50", the key size must be less that 25 bytes
473 because the UDP packet size is 1400 bytes.
476 For replication test, the user must specify at least two memcached servers.
477 The user can use “—rep_write=” option to enable feature.
481 \-\-servers=10.1.1.1:11211,10.1.1.2:11212 –rep_write=2
483 The above command means that there are 2 replication memcached servers,
484 memaslap will set objects to both server 0 and server 1, get
485 objects which are set to server 0 before from server 1, and also get objects
486 which are set to server 1 before from server 0. If server 0 crashes,
487 memaslap will only get objects from server 1. If server 0 comes
488 back to life again, memaslap will reconnect server 0. If both
489 server 0 and server 1 crash, memaslap will exit.
490 .SS Supports thousands of TCP connections
492 Start memaslap with "\-\-conn_sock=" or "\-n" to enable this
493 feature. Make sure that your system can tests opening thousands of files
494 and creating thousands of sockets. However, this feature does not tests
495 reconnection if sockets disconnect.
499 \-\-threads=8 \-\-concurrency=128 \-\-conn_sock=128
501 The above command means that memaslap starts up 8 threads, each
502 thread has 16 concurrencies, each concurrency has 128 TCP socket
503 connections, and the total number of TCP socket connections is 128 * 128 =
505 .SS Supports binary protocol
507 Start memaslap with "\-\-binary" or "\-B" options to enable this
508 feature. It testss all the above features except UDP, because the latest
509 memcached 1.3.3 does not implement binary UDP protocol.
515 Since memcached 1.3.3 doesn\(aqt implement binary UDP protocol,
516 memaslap does not tests UDP. In addition, memcached 1.3.3 does not tests
517 multi\-get. If you specify "\-\-division=50" option, it just sends 50 get
518 commands together as “mulit\-get” to the server.
519 .SH CONFIGURATION FILE
521 This section describes the format of the configuration file. By default
522 when no configuration file is specified memaslap reads the default
523 one located at ~/.memaslap.cnf.
525 Below is a sample configuration file:
529 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
530 #comments should start with \(aq#\(aq
532 #start_len end_len proportion
534 #key length range from start_len to end_len
535 #start_len must be equal to or greater than 16
536 #end_len must be equal to or less than 250
537 #start_len must be equal to or greater than end_len
538 #memaslap will generate keys according to the key range
539 #proportion: indicates keys generated from one range accounts for the total
542 #example1: key range 16~100 accounts for 80%
543 # key range 101~200 accounts for 10%
544 # key range 201~250 accounts for 10%
545 # total should be 1 (0.8+0.1+0.1 = 1)
551 #example2: all keys length are 128 bytes
557 #start_len end_len proportion
559 #value length range from start_len to end_len
560 #start_len must be equal to or greater than 1
561 #end_len must be equal to or less than 1M
562 #start_len must be equal to or greater than end_len
563 #memaslap will generate values according to the value range
564 #proportion: indicates values generated from one range accounts for the
565 total generated values
567 #example1: value range 1~1000 accounts for 80%
568 # value range 1001~10000 accounts for 10%
569 # value range 10001~100000 accounts for 10%
570 # total should be 1 (0.8+0.1+0.1 = 1)
576 #example2: all value length are 128 bytes
582 #cmd_type cmd_proportion
584 #currently memaslap only testss get and set command.
590 #example: set command accounts for 50%
591 # get command accounts for 50%
592 # total should be 1 (0.5+0.5 = 1)
604 At the beginning, memaslap displays some configuration information as follows:
606 servers : 127.0.0.1:11211
616 set proportion: set_prop=0.10
618 get proportion: get_prop=0.90
624 The servers used by memaslap.
631 The number of threads memaslap runs with.
638 The number of concurrencies memaslap runs with.
645 How long to run memaslap.
652 The task window size of each concurrency.
659 The proportion of set command.
666 The proportion of get command.
670 The output of dynamic statistics is something like this:
674 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
676 Type Time(s) Ops TPS(ops/s) Net(M/s) Get_miss Min(us) Max(us)
677 Avg(us) Std_dev Geo_dist
678 Period 5 345826 69165 65.3 0 27 2198 203
680 Global 20 1257935 62896 71.8 0 26 3791 224
685 Type Time(s) Ops TPS(ops/s) Net(M/s) Get_miss Min(us) Max(us)
686 Avg(us) Std_dev Geo_dist
687 Period 5 38425 7685 7.3 0 42 628 240
689 Global 20 139780 6989 8.0 0 37 3790 253
694 Type Time(s) Ops TPS(ops/s) Net(M/s) Get_miss Min(us) Max(us)
695 Avg(us) Std_dev Geo_dist
696 Period 5 384252 76850 72.5 0 27 2198 207
698 Global 20 1397720 69886 79.7 0 26 3791 227
700 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
708 Statistics information of get command
715 Statistics information of set command
722 Statistics information of both get and set command
729 Result within a period
750 Throughput, operations/second
764 How many objects can’t be gotten
771 The minimum response time
778 The maximum response time
785 The average response time
792 Standard deviation of response time
799 Geometric distribution based on natural exponential function
803 At the end, memaslap will output something like this:
807 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
808 Get Statistics (1257956 events)
816 8: 484890 459823 12543 824
819 Set Statistics (139782 events)
827 8: 50784 65574 2064 167
830 Total Statistics (1397738 events)
838 8: 535674 525397 14607 991
848 written_bytes: 242516030
849 read_bytes: 1003702556
850 object_bytes: 152086080
855 Run time: 20.0s Ops: 1397754 TPS: 69817 Net_rate: 59.4M/s
856 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
864 Get statistics of response time
871 Set statistics of response time
878 Both get and set statistics of response time
885 The accumulated and minimum response time
892 The accumulated and maximum response time
899 The accumulated and average response time
906 Standard deviation of response time
913 Geometric distribution based on logarithm 2
920 Total get commands done
927 Total set commands done
934 How many objects can’t be gotten from server
941 How many objects need to verify but can’t get them
948 How many objects with insistent value
955 How many objects are expired but we get them
962 How many objects are unexpired but we can’t get them
990 How many UDP packages are disorder
997 How many UDP packages are lost
1004 How many times UDP time out happen
1025 Throughput, operations/second
1032 The average rate of network
1038 .B \-s, \-\-servers=
1039 List one or more servers to connect. Servers count must be less than
1040 threads count. e.g.: \-\-servers=localhost:1234,localhost:11211
1042 .B \-T, \-\-threads=
1043 Number of threads to startup, better equal to CPU numbers. Default 8.
1045 .B \-c, \-\-concurrency=
1046 Number of concurrency to simulate with load. Default 128.
1048 .B \-n, \-\-conn_sock=
1049 Number of TCP socks per concurrency. Default 1.
1051 .B \-x, \-\-execute_number=
1052 Number of operations(get and set) to execute for the
1053 given test. Default 1000000.
1056 How long the test to run, suffix: s\-seconds, m\-minutes, h\-hours,
1057 d\-days e.g.: \-\-time=2h.
1059 .B \-F, \-\-cfg_cmd=
1060 Load the configure file to get command,key and value distribution list.
1062 .B \-w, \-\-win_size=
1063 Task window size of each concurrency, suffix: K, M e.g.: \-\-win_size=10k.
1066 .B \-X, \-\-fixed_size=
1067 Fixed length of value.
1070 The proportion of date verification, e.g.: \-\-verify=0.01
1072 .B \-d, \-\-division=
1073 Number of keys to multi\-get once. Default 1, means single get.
1075 .B \-S, \-\-stat_freq=
1076 Frequency of dumping statistic information. suffix: s\-seconds,
1077 m\-minutes, e.g.: \-\-resp_freq=10s.
1079 .B \-e, \-\-exp_verify=
1080 The proportion of objects with expire time, e.g.: \-\-exp_verify=0.01.
1081 Default no object with expire time
1083 .B \-o, \-\-overwrite=
1084 The proportion of objects need overwrite, e.g.: \-\-overwrite=0.01.
1085 Default never overwrite object.
1089 .B \-R, \-\-reconnect
1090 Reconnect tests, when connection is closed it will be reconnected.
1093 UDP tests, default memaslap uses TCP, TCP port and UDP port of
1094 server must be same.
1096 .B \-a, \-\-facebook
1097 Whether it enables facebook test feature, set with TCP and multi\-get with UDP.
1100 Whether it enables binary protocol. Default with ASCII protocol.
1105 Expected throughput, suffix: K, e.g.: \-\-tps=10k.
1107 .B \-p, \-\-rep_write=
1108 The first nth servers can write data, e.g.: \-\-rep_write=2.
1113 Whether it outputs detailed information when verification fails.
1116 Display this message and then exit.
1119 Display the version of the application and then exit.
1123 memaslap \-s 127.0.0.1:11211 \-S 5s
1125 memaslap \-s 127.0.0.1:11211 \-t 2m \-v 0.2 \-e 0.05 \-b
1127 memaslap \-s 127.0.0.1:11211 \-F config \-t 2m \-w 40k \-S 20s \-o 0.2
1129 memaslap \-s 127.0.0.1:11211 \-F config \-t 2m \-T 4 \-c 128 \-d 20 \-P 40k
1131 memaslap \-s 127.0.0.1:11211 \-F config \-t 2m \-d 50 \-a \-n 40
1133 memaslap \-s 127.0.0.1:11211,127.0.0.1:11212 \-F config \-t 2m
1135 memaslap \-s 127.0.0.1:11211,127.0.0.1:11212 \-F config \-t 2m \-p 2
1138 To find out more information please check:
1139 \fI\%http://libmemcached.org/\fP
1142 Mingqiang Zhuang <\fI\%mingqiangzhuang@hengtiansoft.com\fP> (Schooner Technolgy)
1143 Brian Aker, <\fI\%brian@tangent.org\fP>
1146 \fImemcached(1)\fP \fIlibmemcached(3)\fP
1150 2011, Brian Aker DataDifferential, http://datadifferential.com/
1151 .\" Generated by docutils manpage writer.
projects / awesomized / libmemcached / blob