[SERVER-45242] Write performance with w: "majority" Created: 19/Dec/19  Updated: 07/Apr/23  Resolved: 19/Dec/19

Status: Closed
Project: Core Server
Component/s: Performance, Write Ops
Affects Version/s: 4.2.1
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Rodrigo Nascimento Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Microsoft Word run012_mongodb_jira.xlsx    
Participants:

 Description   

In a 3-member replica set, with all members living in the same data center. How much slower will w: "majority" be compared to w: "local"?

During my tests, using YCSB to generate the load, I'm seeing a difference that can vary from 4 times up to 19 times slower depending on the load.

Please, see the spreadsheet for more details.



 Comments   
Comment by Rodrigo Nascimento [ 19/Dec/19 ]

Hi Carl,

I only opened it here because there was a "type": "question" available. 

I don't think I have an issue in my infrastructure since I'm getting low latency across network, disk, and filesystem. But I will post my question in the user group anyway.

Thanks,

– Rodrigo Nascimento

Comment by Carl Champain (Inactive) [ 19/Dec/19 ]

Hi logwriter,

The SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag.

Thank you,
Carl

Comment by Rodrigo Nascimento [ 19/Dec/19 ]

Adding some more info: 

  • The network shows very low-latency between members

    [root@vmongon2 ~]# ping -c 10 vmongon3
     PING vmongon3 (192.168.13.52) 56(84) bytes of data.
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=1 ttl=64 time=0.132 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=2 ttl=64 time=0.087 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=3 ttl=64 time=0.119 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=4 ttl=64 time=0.108 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=5 ttl=64 time=0.135 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=6 ttl=64 time=0.104 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=7 ttl=64 time=0.098 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=8 ttl=64 time=0.089 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=9 ttl=64 time=0.103 ms
     64 bytes from vmongon3 (192.168.13.52): icmp_seq=10 ttl=64 time=0.079 ms--- vmongon3 ping statistics ---
     10 packets transmitted, 10 received, 0% packet loss, time 9000ms
     rtt min/avg/max/mdev = 0.079/0.105/0.135/0.019 ms
    [root@vmongon2 ~]# 
    [root@vmongon3 ~]# ping -c 10 vmongon2
     PING vmongon2 (192.168.13.51) 56(84) bytes of data.
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=1 ttl=64 time=0.138 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=2 ttl=64 time=0.088 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=3 ttl=64 time=0.123 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=4 ttl=64 time=0.100 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=5 ttl=64 time=0.088 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=6 ttl=64 time=0.103 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=7 ttl=64 time=0.114 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=8 ttl=64 time=0.089 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=9 ttl=64 time=0.134 ms
     64 bytes from vmongon2 (192.168.13.51): icmp_seq=10 ttl=64 time=0.082 ms--- vmongon2 ping statistics ---
     10 packets transmitted, 10 received, 0% packet loss, time 8999ms
     rtt min/avg/max/mdev = 0.082/0.105/0.138/0.023 ms
     [root@vmongon3 ~]#
    

 

Generated at Thu Feb 08 05:08:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.