{"id":18470,"date":"2022-08-17T08:00:58","date_gmt":"2022-08-17T06:00:58","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=18470"},"modified":"2024-09-10T15:54:40","modified_gmt":"2024-09-10T13:54:40","slug":"mysql-server-on-microsoft-azure-2nd-part-performance-tests","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/mysql-server-on-microsoft-azure-2nd-part-performance-tests\/","title":{"rendered":"MySQL Server on Microsoft Azure 2nd part (Performance tests)"},"content":{"rendered":"\n
\"\"
Azure Database for MySQL<\/figcaption><\/figure>\n\n\n\n

Introduction<\/h2>\n\n\n\n

This second blog follows the first blog about deploying MySQL Server on Microsoft Azure<\/a>. In the first blog, we saw how easy it is to deploy a MySQL server in minutes on the Azure cloud and we connected on it through the MySQL Shell client.<\/p>\n\n\n\n


This second blog is more focused on the performance of MySQL in the Azure Cloud. Although I didn’t do any tuning of MySQL parameters, we will see the influence of MySQL Server localization on the latency as well as changes in parameters such as CPU, memory or IOPS on performances using the SysBench tool.<\/p>\n\n\n\n

SysBench stress test<\/h2>\n\n\n\n

Of course there are many tools available to do stress tests. On my side, I decided to use SysBench simply because I know this wonderful free tool and because it is widely deployed. Rather than making a description of SysBench, I simply take a part of its description available on sourceforge that we can find below: <\/p>\n\n\n\n

sysbench is a scriptable multi-threaded benchmark tool based on LuaJIT. It is most frequently used for database benchmarks, but can also be used to create arbitrarily complex workloads that do not involve a database server <\/em>– https:\/\/sourceforge.net\/projects\/sysbench.mirror\/<\/a>, 14.08.2022<\/p><\/blockquote>\n\n\n\n

Firstly I installed SysBench on my local Ubuntu client (osboxes). After the installation of SysBench but before starting the stress test, we first have to prepare the tables containing the records where the queries will be performed. In the following tests I created 10 tables with 1’000’000 rows in sysbench database (previously created). <\/p>\n\n\n\n

osboxes@osboxes:\/usr\/bin$ sysbench --db-driver=mysql table-size=1000000 --mysql-host=albatroz.mysql.database.azure.com --mysql-port=3306 --mysql-db=sysbench --mysql-user=grs --tables=10 --mysql-password=MyPassword --test=\/usr\/share\/sysbench\/oltp_read_write.lua prepare<\/code><\/pre>\n\n\n\n
Once the tables populated, we can run the tests. For the tests, I decided to use oltp_read_write.lua which has a default ratio of read:write 95%:5%.<\/p>\n\n\n\n
sysbench --db-driver=mysql  --num-threads=8 --mysql-user=grs --mysql-password=MyPassword --mysql-db=sysbench --events=0 --time=100  --test=\/usr\/share\/sysbench\/oltp_read_write.lua --mysql-host=albatroz.mysql.database.azure.com --mysql-port=3306 --tables=10 --db-ps-mode=disable --table-size=1000000 --report-interval=10 run<\/code><\/pre>\n\n\n\n
 I varied the number of threads (num-threads parameter) from 8 to 256, limited the time to 100 seconds and changed two kinds of parameters through the Azure interface during my tests: <\/p>\n\n\n\n