Merge lp:~kent/libmemcached/KBDocs1 into lp:~tangent-org/libmemcached/trunk
- KBDocs1
- Merge into trunk
Proposed by
KentBozlinski
Status: | Merged |
---|---|
Merge reported by: | Brian Aker |
Merged at revision: | not available |
Proposed branch: | lp:~kent/libmemcached/KBDocs1 |
Merge into: | lp:~tangent-org/libmemcached/trunk |
Diff against target: |
472 lines (+78/-77) 17 files modified
docs/hashkit_create.rst (+2/-2) docs/libmemcached.rst (+18/-11) docs/memcached_callback.rst (+25/-27) docs/memcached_delete.rst (+2/-2) docs/memcached_dump.rst (+2/-2) docs/memcached_get.rst (+4/-4) docs/memcached_memory_allocators.rst (+1/-1) docs/memcached_result_st.rst (+4/-4) docs/memcached_sasl.rst (+1/-1) docs/memcached_set.rst (+5/-5) docs/memcached_version.rst (+1/-1) docs/memcapable.rst (+5/-5) docs/memcp.rst (+2/-3) docs/memdump.rst (+1/-1) docs/memerror.rst (+2/-2) docs/memflush.rst (+1/-1) docs/memslap.rst (+2/-5) |
To merge this branch: | bzr merge lp:~kent/libmemcached/KBDocs1 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Libmemcached-developers | Pending | ||
Review via email: mp+58012@code.launchpad.net |
Commit message
Description of the change
Cleaned up Grammar and some formatting of text in some of the docs. No big changes, just cleanup.
To post a comment you must log in.
lp:~kent/libmemcached/KBDocs1
updated
- 937. By Kent <kent@KentLaptop>
-
Merge of Brian with Doc
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1 | === modified file 'docs/hashkit_create.rst' |
2 | --- docs/hashkit_create.rst 2011-04-14 04:27:08 +0000 |
3 | +++ docs/hashkit_create.rst 2011-04-18 19:22:31 +0000 |
4 | @@ -22,9 +22,9 @@ |
5 | |
6 | .. code-block:: perl |
7 | |
8 | - #include <libmemcached/hashkit.h> |
9 | +#include <libmemcached/hashkit.h> |
10 | |
11 | - hashkit_st *hashkit_create(hashkit_st *hash); |
12 | +hashkit_st *hashkit_create(hashkit_st *hash); |
13 | |
14 | hashkit_st *hashkit_clone(hashkit_st *destination, const hashkit_st *ptr); |
15 | |
16 | |
17 | === modified file 'docs/libmemcached.rst' |
18 | --- docs/libmemcached.rst 2011-04-14 04:27:08 +0000 |
19 | +++ docs/libmemcached.rst 2011-04-18 19:22:31 +0000 |
20 | @@ -6,10 +6,17 @@ |
21 | SYNOPSIS |
22 | -------- |
23 | |
24 | -#include <libmemcached/memcached.h> |
25 | - |
26 | -Compile and link with -lmemcached |
27 | - |
28 | +libMemcached is an open source C/C++ client library and tools for the memcached server (http://danga.com/memcached). It has been designed to be light on memory usage, thread safe, and provide full access to server side methods. |
29 | + |
30 | +libMemcached was designed to provide the greatest number of options to use Memcached. Some of the features provided: |
31 | + |
32 | +1. Asynchronous and Synchronous Transport Support. |
33 | +2. Consistent Hashing and Distribution. |
34 | +3. Tunable Hashing algorithm to match keys. |
35 | +4. Access to large object support. |
36 | +5. Local replication. |
37 | +6. A complete reference guide and documentation to the API. |
38 | +7. Tools to Manage your Memcached networks. |
39 | |
40 | ----------- |
41 | DESCRIPTION |
42 | @@ -21,14 +28,14 @@ |
43 | applications by alleviating database load." `http://danga.com/memcached/ <http://danga.com/memcached/>`_ |
44 | |
45 | \ **libmemcached**\ is a small, thread-safe client library for the |
46 | -memcached protocol. The code has all been written with an eye to allow |
47 | +memcached protocol. The code has all been written to allow |
48 | for both web and embedded usage. It handles the work behind routing |
49 | -particular keys to specific servers that you specify (and values are |
50 | -matched based on server order as supplied by you). It implements both |
51 | -a modula and consistent method of object distribution. |
52 | +individual keys to specific servers specified by the developer (and values are |
53 | +matched based on server order as supplied by the user). It implements |
54 | +a modular and consistent method of object distribution. |
55 | |
56 | There are multiple implemented routing and hashing methods. See the |
57 | -memcached_behavior_set() manpage. |
58 | +memcached_behavior_set() manpage for more information. |
59 | |
60 | All operations are performed against a \ ``memcached_st``\ structure. |
61 | These structures can either be dynamically allocated or statically |
62 | @@ -117,9 +124,9 @@ |
63 | --------------------- |
64 | |
65 | |
66 | -When using threads or forked processes it is important to keep an instance |
67 | +When using threads or forked processes it is important to keep one instance |
68 | of \ ``memcached_st``\ per process or thread. Without creating your own locking |
69 | -structures you can not share a single \ ``memcached_st``\ . You can though call |
70 | +structures you can not share a single \ ``memcached_st``\ . However, you can call |
71 | memcached_quit(3) on a \ ``memcached_st``\ and then use the resulting cloned |
72 | structure. |
73 | |
74 | |
75 | === modified file 'docs/memcached_callback.rst' |
76 | --- docs/memcached_callback.rst 2011-04-14 04:27:08 +0000 |
77 | +++ docs/memcached_callback.rst 2011-04-18 19:22:31 +0000 |
78 | @@ -41,73 +41,71 @@ |
79 | memcached_callback_set() changes the function/structure assigned by a |
80 | callback flag. No connections are reset. |
81 | |
82 | -You can use MEMCACHED_CALLBACK_USER_DATA to provide custom context if required for any |
83 | -of the callbacks |
84 | +You can use MEMCACHED_CALLBACK_USER_DATA to provide custom context if required for any of the callbacks. |
85 | |
86 | |
87 | .. c:var:: MEMCACHED_CALLBACK_CLEANUP_FUNCTION |
88 | |
89 | - When memcached_delete() is called this function will be excuted. At the |
90 | - point of its execution all connections have been closed. |
91 | +When memcached_delete() is called this function will be excuted. At the point of its execution all connections are closed. |
92 | |
93 | |
94 | |
95 | .. c:var:: MEMCACHED_CALLBACK_CLONE_FUNCTION |
96 | |
97 | - When memcached_delete() is called this function will be excuted. At the |
98 | - point of its execution all connections have been closed. |
99 | +When memcached_delete() is called this function will be excuted. At the |
100 | +point of its execution all connections are closed. |
101 | |
102 | |
103 | |
104 | .. c:var:: MEMCACHED_CALLBACK_PREFIX_KEY |
105 | |
106 | - You can set a value which will be used to create a domain for your keys. |
107 | - The value specified here will be prefixed to each of your keys. The value can not |
108 | - be greater then MEMCACHED_PREFIX_KEY_MAX_SIZE - 1 and will reduce MEMCACHED_MAX_KEY by |
109 | - the value of your key. The prefix key is only applied to the primary key, |
110 | - not the master key. MEMCACHED_FAILURE will be returned if no key is set. In the case |
111 | - of a key which is too long MEMCACHED_BAD_KEY_PROVIDED will be returned. |
112 | +You can set a value which will be used to create a domain for your keys. |
113 | +The value specified here will be prefixed to each of your keys. The value can not be greater then MEMCACHED_PREFIX_KEY_MAX_SIZE - 1 and will reduce MEMCACHED_MAX_KEY by the value of your key. |
114 | + |
115 | +The prefix key is only applied to the primary key, not the master key. MEMCACHED_FAILURE will be returned if no key is set. In the case of a key which is too long, MEMCACHED_BAD_KEY_PROVIDED will be returned. |
116 | |
117 | - If you set a value with the value being NULL then the prefix key is disabled. |
118 | +If you set a value with the value being NULL then the prefix key is disabled. |
119 | |
120 | |
121 | .. c:var:: MEMCACHED_CALLBACK_USER_DATA |
122 | |
123 | - This allows you to store a pointer to a specifc piece of data. This can be |
124 | - retrieved from inside of memcached_fetch_execute(). Cloning a memcached_st |
125 | - will copy the pointer to the clone. |
126 | +This allows you to store a pointer to a specifc piece of data. This can be |
127 | +retrieved from inside of memcached_fetch_execute(). Cloning a memcached_st |
128 | +will copy the pointer to the clone. |
129 | |
130 | |
131 | |
132 | .. c:var:: MEMCACHED_CALLBACK_MALLOC_FUNCTION |
133 | |
134 | - DEPRECATED: use memcached_set_memory_allocators instead. |
135 | +DEPRECATED: use memcached_set_memory_allocators instead. |
136 | |
137 | |
138 | |
139 | .. c:var:: MEMCACHED_CALLBACK_REALLOC_FUNCTION |
140 | |
141 | - DEPRECATED: use memcached_set_memory_allocators instead. |
142 | +DEPRECATED: use memcached_set_memory_allocators instead. |
143 | |
144 | |
145 | |
146 | .. c:var:: MEMCACHED_CALLBACK_FREE_FUNCTION |
147 | |
148 | - DEPRECATED: use memcached_set_memory_allocators instead. |
149 | +DEPRECATED: use memcached_set_memory_allocators instead. |
150 | |
151 | |
152 | |
153 | .. c:var:: MEMCACHED_CALLBACK_GET_FAILURE |
154 | |
155 | - This function implements the read through cache behavior. On failure of retrieval this callback will be called. |
156 | - You are responsible for populating the result object provided. This result object will then be stored in the server and |
157 | - returned to the calling process. You must clone the memcached_st in order to |
158 | - make use of it. The value will be stored only if you return |
159 | - MEMCACHED_SUCCESS or MEMCACHED_BUFFERED. Returning MEMCACHED_BUFFERED will |
160 | - cause the object to be buffered and not sent immediatly (if this is the default behavior based on your connection setup this will happen automatically). |
161 | +This function implements the read through cache behavior. On failure of retrieval this callback will be called. |
162 | + |
163 | +You are responsible for populating the result object provided. This result object will then be stored in the server and returned to the calling process. |
164 | + |
165 | +You must clone the memcached_st in order to |
166 | +make use of it. The value will be stored only if you return |
167 | +MEMCACHED_SUCCESS or MEMCACHED_BUFFERED. Returning MEMCACHED_BUFFERED will |
168 | +cause the object to be buffered and not sent immediatly (if this is the default behavior based on your connection setup this will happen automatically). |
169 | |
170 | - The prototype for this is: |
171 | - memcached_return_t (\*memcached_trigger_key)(memcached_st \*ptr, char \*key, size_t key_length, memcached_result_st \*result); |
172 | +The prototype for this is: |
173 | +memcached_return_t (\*memcached_trigger_key)(memcached_st \*ptr, char \*key, size_t key_length, memcached_result_st \*result); |
174 | |
175 | |
176 | |
177 | |
178 | === modified file 'docs/memcached_delete.rst' |
179 | --- docs/memcached_delete.rst 2011-04-14 04:27:08 +0000 |
180 | +++ docs/memcached_delete.rst 2011-04-18 19:22:31 +0000 |
181 | @@ -25,8 +25,8 @@ |
182 | find the given value. |
183 | |
184 | Expiration works by placing the item into a delete queue, which means that |
185 | -it won't possible to retrieve it by the "get" command, but "add" and |
186 | -"replace" command with this key will also fail (the "set" command will |
187 | +it won't be possible to retrieve it by the "get" command. The "add" and |
188 | +"replace" commands with this key will also fail (the "set" command will |
189 | succeed, however). After the time passes, the item is finally deleted from server memory. |
190 | |
191 | Please note the the Danga memcached server removed tests for expiration in |
192 | |
193 | === modified file 'docs/memcached_dump.rst' |
194 | --- docs/memcached_dump.rst 2011-04-14 04:27:08 +0000 |
195 | +++ docs/memcached_dump.rst 2011-04-18 19:22:31 +0000 |
196 | @@ -42,12 +42,12 @@ |
197 | ----------- |
198 | |
199 | |
200 | -memcached_dump() is used to get a list of keys found memcached(1) servers. |
201 | +memcached_dump() is used to get a list of keys found in memcached(1) servers. |
202 | Because memcached(1) does not guarentee to dump all keys you can not assume |
203 | you have fetched all keys from the server. The function takes an array |
204 | of callbacks that it will use to execute on keys as they are found. |
205 | |
206 | -Currently the binar protocol is not testsed. |
207 | +Currently the binary protocol is not testsed. |
208 | |
209 | |
210 | ------ |
211 | |
212 | === modified file 'docs/memcached_get.rst' |
213 | --- docs/memcached_get.rst 2011-04-14 04:27:08 +0000 |
214 | +++ docs/memcached_get.rst 2011-04-18 19:22:31 +0000 |
215 | @@ -65,7 +65,7 @@ |
216 | upon success and NULL will be returned on failure. MEMCACHD_END is returned |
217 | by the \*error value when all objects that have been found are returned. |
218 | The final value upon MEMCACHED_END is null. Values returned by |
219 | -memcached_fetch() musted be free'ed by the caller. memcached_fetch() will |
220 | +memcached_fetch() must be freed by the caller. memcached_fetch() will |
221 | be DEPRECATED in the near future, memcached_fetch_result() should be used |
222 | instead. |
223 | |
224 | @@ -89,7 +89,7 @@ |
225 | similar to memcached_mget(), but it may trigger the supplied callbacks |
226 | with result sets while sending out the queries. If you try to perform |
227 | a really large multiget with memcached_mget() you may encounter a |
228 | -deadlock in the OS kernel (we fail to write data to the socket because |
229 | +deadlock in the OS kernel (it will fail to write data to the socket because |
230 | the input buffer is full). memcached_mget_execute() solves this |
231 | problem by processing some of the results before continuing sending |
232 | out requests. Please note that this function is only available in the |
233 | @@ -100,9 +100,9 @@ |
234 | a master key that is used for determining which server an object was stored |
235 | if key partitioning was used for storage. |
236 | |
237 | -All of the above functions are not testsed when the \ ``MEMCACHED_BEHAVIOR_USE_UDP``\ |
238 | +All of the above functions are not tested when the \ ``MEMCACHED_BEHAVIOR_USE_UDP``\ |
239 | has been set. Executing any of these functions with this behavior on will result in |
240 | -\ ``MEMCACHED_NOT_SUPPORTED``\ being returned or, for those functions which do not return |
241 | +\ ``MEMCACHED_NOT_SUPPORTED``\ being returned, or for those functions which do not return |
242 | a \ ``memcached_return_t``\ , the error function parameter will be set to |
243 | \ ``MEMCACHED_NOT_SUPPORTED``\ . |
244 | |
245 | |
246 | === modified file 'docs/memcached_memory_allocators.rst' |
247 | --- docs/memcached_memory_allocators.rst 2011-04-14 04:27:08 +0000 |
248 | +++ docs/memcached_memory_allocators.rst 2011-04-18 19:22:31 +0000 |
249 | @@ -45,7 +45,7 @@ |
250 | ----------- |
251 | |
252 | |
253 | -libmemcached(3) allows you to specify your own memory allocators optimized |
254 | +libmemcached(3) allows you to specify your own memory allocators, optimized |
255 | for your application. This enables libmemcached to be used inside of applications that have their own malloc implementation. |
256 | |
257 | memcached_set_memory_allocators() is used to set the memory allocators used |
258 | |
259 | === modified file 'docs/memcached_result_st.rst' |
260 | --- docs/memcached_result_st.rst 2011-04-14 04:27:08 +0000 |
261 | +++ docs/memcached_result_st.rst 2011-04-18 19:22:31 +0000 |
262 | @@ -59,9 +59,9 @@ |
263 | |
264 | libmemcached(3) can optionally return a memcached_result_st which acts as a |
265 | result object. The result objects have added benefits over the character |
266 | -pointer returns in that they are forward compatible with new return items |
267 | +pointer returns, in that they are forward compatible with new return items |
268 | that future memcached servers may implement (the best current example of |
269 | -this is the CAS return item). The structures can also be reused which will |
270 | +this is the CAS return item). The structures can also be reused, which will |
271 | save on calls to malloc(3). It is suggested that you use result objects over |
272 | char \* return functions. |
273 | |
274 | @@ -72,7 +72,7 @@ |
275 | memcached_result_st or will initialize a structure passed to it. |
276 | |
277 | memcached_result_free() will deallocate any memory attached to the |
278 | -structure. If the structure was also alloacted, it will deallocate it. |
279 | +structure. If the structure was also allocated, it will deallocate it. |
280 | |
281 | memcached_result_key_value() returns the key value associated with the |
282 | current result object. |
283 | @@ -91,7 +91,7 @@ |
284 | |
285 | memcached_result_cas() returns the cas associated with the |
286 | current result object. This value will only be available if the server |
287 | -testss it. |
288 | +tests it. |
289 | |
290 | memcached_result_set_value() takes a byte array and a size and sets |
291 | the result to this value. This function is used for trigger responses. |
292 | |
293 | === modified file 'docs/memcached_sasl.rst' |
294 | --- docs/memcached_sasl.rst 2011-04-09 00:46:34 +0000 |
295 | +++ docs/memcached_sasl.rst 2011-04-18 19:22:31 +0000 |
296 | @@ -44,7 +44,7 @@ |
297 | Please note that SASL requires the memcached binary protocol, and you have |
298 | to specify the callbacks before you connect to the server. |
299 | |
300 | -memcached_set_sasl_auth_data() is a helper function for you defining |
301 | +memcached_set_sasl_auth_data() is a helper function defining |
302 | the basic functionality for you, but it will store the username and password |
303 | in memory. If you choose to use this method you have to call |
304 | memcached_destroy_sasl_auth_data before calling memcached_free to avoid |
305 | |
306 | === modified file 'docs/memcached_set.rst' |
307 | --- docs/memcached_set.rst 2011-04-14 04:27:08 +0000 |
308 | +++ docs/memcached_set.rst 2011-04-18 19:22:31 +0000 |
309 | @@ -49,8 +49,8 @@ |
310 | memcached_set(), memcached_add(), and memcached_replace() are all used to |
311 | store information on the server. All methods take a key, and its length to |
312 | store the object. Keys are currently limited to 250 characters by the |
313 | -memcached(1) server. You must also supply a value and a length. Optionally you |
314 | -may tests an expiration time for the object and a 16 byte value (it is |
315 | +memcached(1) server. You must supply both a value and a length. Optionally you |
316 | +may test an expiration time for the object and a 16 byte value (it is |
317 | meant to be used as a bitmap). |
318 | |
319 | memcached_set() will write an object to the server. If an object already |
320 | @@ -87,12 +87,12 @@ |
321 | the fastest way to store data on the server. |
322 | |
323 | All of the above functions are testsed with the \ ``MEMCACHED_BEHAVIOR_USE_UDP``\ |
324 | -behavior enabled. But when using these operations with this behavior on, there |
325 | +behavior enabled. However, when using these operations with this behavior on, there |
326 | are limits to the size of the payload being sent to the server. The reason for |
327 | -these limits is that the Memcahed Server does not allow multi-datagram requests |
328 | +these limits is that the Memcached Server does not allow multi-datagram requests |
329 | and the current server implementation sets a datagram size to 1400 bytes. Due |
330 | to protocol overhead, the actual limit of the user supplied data is less than |
331 | -1400 bytes and depends on the protocol in use as well as the operation being |
332 | +1400 bytes and depends on the protocol in use as, well as the operation being |
333 | executed. When running with the binary protocol, \ `` MEMCACHED_BEHAVIOR_BINARY_PROTOCOL``\ , |
334 | the size of the key,value, flags and expiry combined may not exceed 1368 bytes. |
335 | When running with the ASCII protocol, the exact limit fluctuates depending on |
336 | |
337 | === modified file 'docs/memcached_version.rst' |
338 | --- docs/memcached_version.rst 2011-04-14 04:27:08 +0000 |
339 | +++ docs/memcached_version.rst 2011-04-18 19:22:31 +0000 |
340 | @@ -39,7 +39,7 @@ |
341 | |
342 | |
343 | memcached_lib_version() is used to return a simple version string representing |
344 | -the libmemcached version (version of the client library, not server) |
345 | +the libmemcached version (client library version, not server version) |
346 | |
347 | memcached_version() is used to set the major, minor, and micro versions of each |
348 | memcached server being used by the memcached_st connection structure. It returns the |
349 | |
350 | === modified file 'docs/memcapable.rst' |
351 | --- docs/memcapable.rst 2011-04-14 04:27:08 +0000 |
352 | +++ docs/memcapable.rst 2011-04-18 19:22:31 +0000 |
353 | @@ -16,29 +16,29 @@ |
354 | |
355 | .. option:: -h hostname |
356 | |
357 | - Specify the hostname to connect to. The default is \ *localhost*\ |
358 | +Specify the hostname to connect to. The default is \ *localhost*\ |
359 | |
360 | .. option:: -p port |
361 | |
362 | - Specify the port number to connect to. The default is \ *11211*\ |
363 | +Specify the port number to connect to. The default is \ *11211*\ |
364 | |
365 | |
366 | |
367 | .. option:: -c |
368 | |
369 | - Generate a coredump when it detects an error from the server. |
370 | +Generate a coredump when it detects an error from the server. |
371 | |
372 | |
373 | |
374 | .. option:: -v |
375 | |
376 | - Print out the comparison when it detects an error from the server. |
377 | +Print out the comparison when it detects an error from the server. |
378 | |
379 | |
380 | |
381 | .. option:: -t n |
382 | |
383 | - Set the timeout from an IO operation to/from the server to \ *n*\ seconds. |
384 | +Set the timeout from an IO operation to/from the server to \ *n*\ seconds. |
385 | |
386 | ----------- |
387 | DESCRIPTION |
388 | |
389 | === modified file 'docs/memcp.rst' |
390 | --- docs/memcp.rst 2011-04-14 04:27:08 +0000 |
391 | +++ docs/memcp.rst 2011-04-18 19:22:31 +0000 |
392 | @@ -26,11 +26,10 @@ |
393 | It is similar to the standard UNIX cp(1) command. |
394 | |
395 | The key names will be the names of the files, |
396 | -without any directory path part. |
397 | +without any directory path. |
398 | |
399 | You can specify servers via the \ **--servers**\ option or via the |
400 | -environment variable \ ``MEMCACHED_SERVERS``\ . If you specify neither of |
401 | -these, the final value in the command line list is the name of a |
402 | +environment variable \ ``MEMCACHED_SERVERS``\. If you do not specify either these, the final value in the command line list is the name of a |
403 | server(s). |
404 | |
405 | For a full list of operations run the tool with the \ **--help**\ option. |
406 | |
407 | === modified file 'docs/memdump.rst' |
408 | --- docs/memdump.rst 2011-04-14 04:27:08 +0000 |
409 | +++ docs/memdump.rst 2011-04-18 19:22:31 +0000 |
410 | @@ -21,7 +21,7 @@ |
411 | ----------- |
412 | |
413 | |
414 | -\ **memdump**\ currently dumps a list of "keys" from all servers that |
415 | +\ **memdump**\ dumps a list of "keys" from all servers that |
416 | it is told to fetch from. Because memcached does not guarentee to |
417 | provide all keys it is not possible to get a complete "dump". |
418 | |
419 | |
420 | === modified file 'docs/memerror.rst' |
421 | --- docs/memerror.rst 2011-04-14 04:27:08 +0000 |
422 | +++ docs/memerror.rst 2011-04-18 19:22:31 +0000 |
423 | @@ -3,7 +3,7 @@ |
424 | ============================================== |
425 | |
426 | |
427 | -Translate a memcached error code to a string |
428 | +Translates a memcached error code into a string |
429 | |
430 | |
431 | -------- |
432 | @@ -21,7 +21,7 @@ |
433 | ----------- |
434 | |
435 | |
436 | -\ **memerror**\ translate an error code from libmemcached(3) to a human |
437 | +\ **memerror**\ translate an error code from libmemcached(3) into a human |
438 | readable string. |
439 | |
440 | For a full list of operations run the tool with the \ **--help**\ option. |
441 | |
442 | === modified file 'docs/memflush.rst' |
443 | --- docs/memflush.rst 2011-04-14 04:27:08 +0000 |
444 | +++ docs/memflush.rst 2011-04-18 19:22:31 +0000 |
445 | @@ -22,7 +22,7 @@ |
446 | |
447 | |
448 | \ **memflush**\ resets the contents of memcached(1) servers. |
449 | -This means all data in these servers will be deleted. |
450 | +This means that all data in the specified servers will be deleted. |
451 | |
452 | You can specify servers via the \ **--servers**\ option or via the |
453 | environment variable \ ``MEMCACHED_SERVERS``\ . |
454 | |
455 | === modified file 'docs/memslap.rst' |
456 | --- docs/memslap.rst 2011-04-11 05:22:20 +0000 |
457 | +++ docs/memslap.rst 2011-04-18 19:22:31 +0000 |
458 | @@ -20,12 +20,9 @@ |
459 | |
460 | |
461 | \ **memslap**\ is a load generation and benchmark tool for memcached(1) |
462 | -servers. It generates configurable workload such as threads, concurrencies, connections, |
463 | -run time, overwrite, miss rate, key size, value size, get/set proportion, |
464 | -expected throughput, and so on. |
465 | +servers. It generates configurable workload such as threads, concurrencies, connections, run time, overwrite, miss rate, key size, value size, get/set proportion, expected throughput, and so on. |
466 | |
467 | -You can specify servers via the \ **--servers**\ option or via the |
468 | -environment variable \ ``MEMCACHED_SERVERS``\ . |
469 | +You can specify servers via the \ **--servers**\ option or via the environment variable \ ``MEMCACHED_SERVERS``\ . |
470 | |
471 | |
472 | -------- |