<span id="mktg5"></span>

<i id="mktg5"><meter id="mktg5"></meter></i>

        <label id="mktg5"><meter id="mktg5"></meter></label>
        最新文章專題視頻專題問答1問答10問答100問答1000問答2000關(guān)鍵字專題1關(guān)鍵字專題50關(guān)鍵字專題500關(guān)鍵字專題1500TAG最新視頻文章推薦1 推薦3 推薦5 推薦7 推薦9 推薦11 推薦13 推薦15 推薦17 推薦19 推薦21 推薦23 推薦25 推薦27 推薦29 推薦31 推薦33 推薦35 推薦37視頻文章20視頻文章30視頻文章40視頻文章50視頻文章60 視頻文章70視頻文章80視頻文章90視頻文章100視頻文章120視頻文章140 視頻2關(guān)鍵字專題關(guān)鍵字專題tag2tag3文章專題文章專題2文章索引1文章索引2文章索引3文章索引4文章索引5123456789101112131415文章專題3
        問答文章1 問答文章501 問答文章1001 問答文章1501 問答文章2001 問答文章2501 問答文章3001 問答文章3501 問答文章4001 問答文章4501 問答文章5001 問答文章5501 問答文章6001 問答文章6501 問答文章7001 問答文章7501 問答文章8001 問答文章8501 問答文章9001 問答文章9501
        當前位置: 首頁 - 科技 - 知識百科 - 正文

        Semi-SyncreplicationperformanceinMySQL5.7.4DMR_MySQL

        來源:懂視網(wǎng) 責編:小采 時間:2020-11-09 19:20:24
        文檔

        Semi-SyncreplicationperformanceinMySQL5.7.4DMR_MySQL

        Semi-SyncreplicationperformanceinMySQL5.7.4DMR_MySQL:I was interested to hear about semi-sync replication improvements in MySQLs 5.7.4 DMR release and decided to check it out. I previouslyblogged about poor semi-sync performanceand
        推薦度:
        導讀Semi-SyncreplicationperformanceinMySQL5.7.4DMR_MySQL:I was interested to hear about semi-sync replication improvements in MySQLs 5.7.4 DMR release and decided to check it out. I previouslyblogged about poor semi-sync performanceand

        I was interested to hear about semi-sync replication improvements in MySQL’s 5.7.4 DMR release and decided to check it out. I previouslyblogged about poor semi-sync performanceand was pretty disappointed from semi-sync’s performance across WAN distances back then, particularly with many client threads.

        The Test

        The basic environment of these tests was:

      1. AWS EC2 m3.medium instances
      2. Master in us-east-1, slave in us-west-1 (~78ms ping RTT)
      3. CentOS 6.5
      4. innodb_flush_log_at_trx_commit=1
      5. sync_binlog=1
      6. Semi-sync replication plugin installed and enabled.
      7. GTID’s enabled (except on 5.5)
      8. sysbench 0.5 update_index.lua test, 60 seconds, 250k table size.
      9. MySQL 5.7 was tested with both AFTER_SYNC and AFTER_COMMIT settings forrpl_semi_sync_master_wait_point
      10. I tested Percona XtraDB Cluster 5.6 / Galera 3.5 as well by means of comparison
      11. Without further ado, here’s the TpmC results I got for a single client thread:

        These graphs are interactive, so mouse-over for more details. I’m using log scales to better highlight the differences.

        The blue bars represent transactions per second (more is better). The red bars represent average latency per transaction per client (less is better). Remember these transactions are synchronously being copied across the US before the client can execute another.

        The first test is our control: Async allows ~273 TPS on a single thread. Once we introduce synchronicity, we clearly see the bulk of the time is that round trip. Note that MySQL 5.5 and 5.6 are a bit higher than MySQL 5.7 and Percona XtraDB Cluster, the latter of which show pretty similar results.

        Adding parallelism

        This gets more interesting to see if we redo the same tests, but with 32 test threads:

        In the MySQL 5.5 and 5.6 tests, we can clearly see nasty serialization. Both really don’t allow more performance than single threaded sysbench. I was happy to see, however, that this seems to be dramatically improved in MySQL 5.7, nice job Oracle!

        AFTER_SYNC and AFTER_COMMIT vary, but AFTER_SYNC is the default and is preferred over AFTER_COMMIT. The reasoning here is AFTER_SYNC forces the semi-sync wait BEFORE the transaction is committed on the master. The client still must wait for the semi-sync in AFTER_COMMIT, but other transactions may see its data on the master BEFORE we confirm the semi-sync slave has received it. This is potentially bad because if the master crashed at that instant, clients may have read data from the master that did not make it to a failover slave. This is a type of ‘phantom read’ andYoshinori explains it in more detail here.

        What about Percona XtraDB Cluster?

        I also want to discuss the Percona XtraDB Cluster results, Galera here is somewhat slower than MySQL 5.7 semi-sync. There may be some enhancements to Galera that can be made (competition is a good thing), but there are still some significant differences here:

      12. Galera allows for writing on any and all nodes, semi-sync does not
      13. Galera introduces the certification process to check for conflicts, Semi-sync does not
      14. Galera is not 2-phase commit and transactions are not committed synchronously anywhere except the node originating the transaction. So, it is similar to Semi-sync in this way.
      15. I ran the Galera tests with no log-bin (Galera does not require it)
      16. I ran the Galera tests with innodb_flush_log_at_trx_commit=1
      17. I set the fc_limit on the second node really high to eliminate Flow control as a bottleneck. In a live cluster, it would typically be needed.
      18. Galera provides parallel slave threads for faster apply, but it doesn’t matter here because I set the fc_limit so high
      19. TL;DR

        Semi-sync in MySQL 5.7 looks like a great improvement. Any form of synchronicity is always going to be expensive, particularly over 10s and 100s of milliseconds of latency. With MySQL 5.7, I’d be much more apt to recommend semi-sync as an option than in previous releases. Thanks to Oracle for investing here.

        聲明:本網(wǎng)頁內(nèi)容旨在傳播知識,若有侵權(quán)等問題請及時與本網(wǎng)聯(lián)系,我們將在第一時間刪除處理。TEL:177 7030 7066 E-MAIL:11247931@qq.com

        文檔

        Semi-SyncreplicationperformanceinMySQL5.7.4DMR_MySQL

        Semi-SyncreplicationperformanceinMySQL5.7.4DMR_MySQL:I was interested to hear about semi-sync replication improvements in MySQLs 5.7.4 DMR release and decided to check it out. I previouslyblogged about poor semi-sync performanceand
        推薦度:
        標簽: 同步 mysql mysql5.7
        • 熱門焦點

        最新推薦

        猜你喜歡

        熱門推薦

        專題
        Top
        主站蜘蛛池模板: 亚洲香蕉久久一区二区 | 国产精品免费久久久久久久久 | 亚洲五月丁香综合视频| 亚洲第一网站免费视频| 亚洲第一中文字幕| 精品无码国产污污污免费网站 | 亚洲一区二区三区无码影院| 高清免费久久午夜精品| 国产亚洲av人片在线观看| 精品国产免费一区二区三区| 日本亚洲视频在线| 精品成在人线AV无码免费看 | 国产精品美女免费视频观看| 亚洲无线码一区二区三区| 丰满人妻一区二区三区免费视频| 国产亚洲精品高清在线| 亚洲精品免费在线观看| 亚洲一区在线观看视频| 国产在线观看www鲁啊鲁免费| 一级毛片成人免费看a| 亚洲成AV人片天堂网无码| 69xx免费观看视频| 亚洲一区二区三区高清在线观看| 成年女人永久免费观看片| 精品在线免费视频| 亚洲乱码中文字幕久久孕妇黑人| 99精品视频在线免费观看 | 久久亚洲高清观看| 久草视频在线免费| 美女一级毛片免费观看| 国产亚洲一区二区三区在线观看 | 亚洲国产精品成人| 亚洲成人免费在线| 国产精品亚洲专区无码唯爱网| 亚洲综合国产一区二区三区| 亚洲一级毛片免费在线观看| 另类专区另类专区亚洲| 亚洲国产精品久久久久久| 波多野结衣久久高清免费 | 暖暖免费日本在线中文| 亚洲综合精品第一页|