Probably have some ideas, draw some mind map, the real implementation may be difficult, but can feedback to hyperpacer, let their technical staff to provide support to write some plug-ins, so in the integration should be easier.
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7F/50/wKiom1cZnsbikXeHAAFQqGvnA1E166.png "title=" Performance test automation construction content. png "alt=" Wkiom1cznsbikxehaafqqgvna1e166.png "/>
The strategy for testing is probably as follows:
650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/7F/50/wKiom1cZnt_CcuJXAADY5iom6BY513.png "title=" Performance testing automates execution policies. png "alt=" Wkiom1cznt_ccujxaady5iom6by513.png "/>
For the storage of information such as running result, monitoring data and so on, for a sustainable performance test system, this information should not be scattered in each load machine, and the special database should be designed for storage.
In terms of operations, there are only two types of operations: INSERT, read, no update or delete, and most of these data are read and written in the database;
Storage, multiple product lines of multiple cycles of test results and monitoring data will be a very large amount of data;
From these two aspects, tokudb just can meet the demand.
The TOKUDB storage engine features high compression ratios and high insert performance, and can be used as a storage for monitoring systems. According to the official test results, the high compression ratio of the tokudb can reach 1:12, while the high insert performance, officially known as 9 times times higher than the InnoDB.
It seems that the use of tokudb is a good choice, it is said that the latest Percona has built-in tokudb, you can use it.
This article from the "Performance Test" blog, reproduced please contact the author!
Automated performance testing based on Hyperpacer