![]() clone_autotune_concurrency If enabled the clone operation uses up to clone_max_concurrency threads.Otherwise, this is the exact number of threads that remote cloning uses. clone_max_concurrency= Defines the maximum number of threads used for a remote cloning operation with autotune enabled.Out of the required parameters to operate the clone plugin, the following were set up accordingly in the recipient server: In the graphs below, lower values are better. These make a total of 54 tests, executed 12+1 times each.Īll times are in seconds. Finally, we executed all the tests using three different network limits: 500mbps, 1000mbps, and 4000mbps. We also tested with and without compression. For the clone plugin, we tested auto (which lets the server decide how many threads will perform the clone) and 1 to 4 threads. In the case of compression, we allocated the same number of threads to compression and decompression. For XtraBackup, we tested 1 to 4 threads, with and without compression. We tested different combinations of clone and Percona XtraBackup operations. This is beyond the scope of this assessment. ![]() Otherwise, we would have to take into consideration things like application response time, or the number of transactions executed. We measured only the clone process, reducing the benchmark complexity. We created the disks on the same datastore.ĭuring the tests, we did not generate additional operations on the database. Both source and replica virtual machines run 4 cores, 8 Gb RAM, and 60Gb storage. We used sysbench to create 200 tables of 124Mb each for a total of 24Gb. The only stage that is sequential is the last one: prepare. These stages can take place in parallel: we can stream the backup to the new server using netcat and, at the same time, we can write it into the destination directory. The cloning process involves several stages: backup, stream, write, and prepare. Percona XtraBackup, on the other side, is a more complex tool. Just issuing a command from the destination database is enough. ![]() Once installed and configured, cloning a database is straightforward. The plugin supports compression only for network transmission, not for storage.īut one of the plugin’s strong points is simplicity. If you need to perform backups, Percona XtraBackup is a better tool as it supports compression and incremental backups, among other features not provided by the plugin. In this blog post, we compare both alternatives for cloning purposes. Before the release of the plugin, the best open-source alternative was Percona XtraBackup for MySQL Databases. It is easy to rebuild a replica or to add new nodes to a cluster using the plugin. The Clone Plugin, available since MySQL 8.0.17, is a great feature that allows cloning databases out of the box. Large replication topologies are quite common nowadays, and this kind of architecture often requires a quick method to rebuild a replica from another server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |