筆者英語不好，又沒人翻譯，只好自己動(dòng)手，希望大家多提意見，我好及時(shí)修改，以免誤導(dǎo)他人。本文僅供參考，筆者對(duì)使用者產(chǎn)生的任何后果，概不負(fù)責(zé)。?? 轉(zhuǎn)載請(qǐng)注明出處！

正文：

The MySQL distribution comes with a rather comprehensive set of generic tests that have been bundled together so you can run them as a group and examine the results. The tests will do little to help you figure out whether a configuration change will speed up your application. But they're very helpful when used as a high-level benchmark, meaning they provide a good overall indication of how well one server performs relative to another.

MySQL分發(fā)包捆綁了一套相當(dāng)全面的系統(tǒng)基準(zhǔn)測(cè)試工具，這樣你就可以單獨(dú)運(yùn)行他們并檢查測(cè)試結(jié)果。每次測(cè)試的結(jié)果對(duì)于確定一個(gè)配置更改是否會(huì)加快您的應(yīng)用程序幫助不大。但作為一個(gè)高層次的基準(zhǔn)，他們非常有幫助，這意味著他們提供一個(gè)良好的整體性能指示，一臺(tái)服務(wù)器性能相對(duì)于另一臺(tái)的整體表現(xiàn)。

You can also run the tests individually if you'd like compare a subset of the results from several servers. If you're mainly interested in UPDATE speed, run one of the UPDATE-intensive tests a few times on each server.

如果你想比較幾臺(tái)服務(wù)器的性能，可以單獨(dú)測(cè)試每臺(tái)服務(wù)器，然后比較測(cè)試結(jié)果。如果你主要想測(cè)試更新速度，每臺(tái)服務(wù)器上多做幾次更新更密集的測(cè)試。

The benchmark suite can be used to test non-MySQL servers as well. According to the README, PostgreSQL, Solid, and mSQL have been tested. This may be helpful if you're trying to choose between MySQL and PostgreSQL. All the benchmark code is relatively generic Perl using the DBI and Benchmark modules. If needed, you can add support for nearly any database server that has a DBI driver (Oracle, Sybase, Informix, DB2, etc.). If you do so, be sure to look at the bench-init.pl for any global options you may need to add or change.

基準(zhǔn)套件，也可以用來測(cè)試非MySQL服務(wù)器。根據(jù)自述文件，PostgreSQL，Solid，mSQL的已經(jīng)過測(cè)試。這個(gè)測(cè)試會(huì)對(duì)你選擇MySQL或PostgreSQL哪種做為數(shù)據(jù)庫(kù)有所幫助。所有基準(zhǔn)的代碼是用相對(duì)通用的Perl語言編寫,使用了DBI和基準(zhǔn)模塊。如果需要，您可以添加具有DBI驅(qū)動(dòng)程序(ORACLE，SYBASE，Informix和DB2等)幾乎所有的數(shù)據(jù)庫(kù)服務(wù)器的支持。如果您這樣做，一定要檢查bench-init.pl文件，尋找任何您可能需要添加或更改的全局選項(xiàng)。

By running the benchmarks against several different servers, you'll get an idea of how much faster one server is than another. The tests are largely CPU-bound, but there are portions of the test that demand a lot of disk I/O (for short times). You'll likely find that the 2.4-GHz CPU doesn't necessarily make MySQL run twice as fast as the 1.2-GHz CPU.

通過對(duì)幾個(gè)不同的服務(wù)器上運(yùn)行基準(zhǔn)測(cè)試，你會(huì)想要知道一臺(tái)服務(wù)器比另一種是快多少。測(cè)試數(shù)據(jù)主要是針對(duì)CPU的，但也有部分的測(cè)試，需求大量的磁盤I / O交換(很短的時(shí)間)。您可能會(huì)發(fā)現(xiàn)，MySQL在2.4 - GHz CPU上的運(yùn)行速度不一定能達(dá)到在1.2 GHz的CPU的運(yùn)行速度的兩倍。

The benchmark suite will not help you test the benefits of multi-CPU machines because the benchmark process is completely serialized. It executes one query after another, so MySQL will not benefit from the addition of a second CPU. To test that, you'll need to use MySQL super-smack or a home-grown solution. Both are covered in the following sections.

基準(zhǔn)套件不能幫助您測(cè)試多核CPU的機(jī)器，因?yàn)榛鶞?zhǔn)測(cè)試的過程完全序列化。它執(zhí)行了一個(gè)又一個(gè)的查詢，所以MySQL不會(huì)從第二個(gè)CPU中受益。為了測(cè)試多核CPU的性能，你需要使用MySQL super-smack或一個(gè)手動(dòng)設(shè)計(jì)的解決方案。下面的章節(jié)將會(huì)講到這些。

To run the tests, use the run-all-tests script located in the sql-bench directory. Be sure to read the README in that directory. It provides a complete list of the command-line options you can use.

運(yùn)行測(cè)試，使用位于sql-bench目錄下的run-all-tests測(cè)試腳本。請(qǐng)務(wù)必閱讀該目錄中的自述。它提供了一個(gè)可以使用的命令行選項(xiàng)的完整列表。

總結(jié)

以上是生活随笔為你收集整理的mysql基准性能测试标准_mysql性能测试与优化——（一），基准测试套件的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。