14.1.4 Testing and Benchmarking with InnoDB

  • If InnoDB is not your default storage engine, you can determine if your database server or applications work correctly with InnoDB by restarting the server with --default-storage-engine=InnoDB defined on the command line or with default-storage-engine=innodb defined in the [mysqld] section of the my.cnf configuration file.
  • 如果InnoDB不是您的默認存儲引擎,您可以通過在命令行中定義 --default-storage-engine=InnoDB 或在my.cnf配置文件的[mysqld]部分中定義的default-storage-engine=innodb 來重新啓動服務器確定您的數據庫服務器或應用程序是否與InnoDB正確地工作。
  • Since changing the default storage engine only affects new tables as they are created, run all your application installation and setup steps to confirm that everything installs properly. Then exercise all the application features to make sure all the data loading, editing, and querying features work. If a table relies on some MyISAM-specific feature, you'll receive an error; add the ENGINE=MyISAM clause to the CREATE TABLE statement to avoid the error,
  • 因爲更改默認存儲引擎僅在創建新表時影響它們,請運行所有應用程序安裝和安裝步驟,以確認一切安裝正確,然後,運行所有應用程序特性,確保所有數據加載、編輯和查詢功能正常工作。如果某個表依賴了一些myisam的特性,你會收到一個錯誤,在CREATE TABLE後面添加ENGINE=MyISAM來避免錯誤
  • If you did not make a deliberate decision about the storage engine, and you just want to preview how certain tables work when they're created under InnoDB, issue the command ALTER TABLE table_name ENGINE=InnoDB; for each table. Or, to run test queries and other statements without disturbing the original table, make a copy like so:
  • 如果您沒有對存儲引擎做出慎重的決定,而你只是想要預覽某些表在InnoDB下創建時是如何工作的,,發出 ALTER TABLE table_name ENGINE=InnoDB命令可以修改每一張表或者想在不干擾原始表的情況下運行測試查詢和其他語句,像這樣複製一份
    14.1.4 Testing and Benchmarking with InnoDB
  • To get a true idea of the performance with a full application under a realistic workload, install the latest MySQL server and run benchmarks.
  • *要在實際工作負載下以完整的應用程序獲取性能的真實情況, 請安裝最新的MySQL服務器並運行基準測試。
  • Test the full application lifecycle, from installation, through heavy usage, and server restart. Kill the server process while the database is busy to simulate a power failure, and verify that the data is recovered successfully when you restart the server.
  • 測試整個應用程序生命週期,從安裝,通過大量使用,再重新啓動服務器。當數據庫忙着模擬電源故障時,殺死服務器進程,並在重新啓動服務器時驗證數據是否成功恢復
  • Test any replication configurations, especially if you use different MySQL versions and options on the master and the slaves.
  • 測試任何複製配置, 尤其是在master和slave使用不同的 MySQL 版本和選項時。。
  • 發表評論
    所有評論
    還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
    相關文章