Author: paul
Date: 2006-01-16 03:42:31 +0100 (Mon, 16 Jan 2006)
New Revision: 846
Log:
r6238@frost: paul | 2006-01-15 18:47:41 -0600
Mention mysqlslap in 5.1 manual for load-testing a server.
Modified:
trunk/
trunk/refman-5.1/optimization.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6235
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2175
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6238
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2175
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2006-01-16 02:40:52 UTC (rev 845)
+++ trunk/refman-5.1/optimization.xml 2006-01-16 02:42:31 UTC (rev 846)
@@ -573,12 +573,34 @@
<para>
To avoid problems like this, you should put some effort into
benchmarking your whole application under the worst possible
- load. You can use Super Smack, available at
- <ulink url="http://jeremy.zawodny.com/mysql/super-smack/"/>. As
- suggested by its name, it can bring a system to its knees if you
- ask it, so make sure to use it only on your development systems.
+ load:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The <command>mysqlslap</command> program can be helpful for
+ simulating a high load produced by multiple clients issuing
+ queries simultaneously. See <xref linkend="mysqlslap"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You can also try Super Smack, available at
+ <ulink url="http://jeremy.zawodny.com/mysql/super-smack/"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ As suggested by the names of these programs, they can bring a
+ system to its knees, so make sure to use them
+ only on your development systems.
+ </para>
+
</section>
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r846 - in trunk: . refman-5.1 | paul | 16 Jan |
