Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-19

MERGE2 slows down traffic

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 2.2.8
    • None
    • None

    Description

      Look into why max and avg values for a stack with MERGE2 are slower than for a stack without MERGE2

      <config>

      <TCP start_port="7800" bind_addr="192.168.0.57" loopback="true"/>

      <TCPPING timeout="3000" initial_hosts="192.168.0.57[7800]" port_range="3" num_initial_members="3"/>

      <MERGE2 min_interval="1500" max_interval="3000" />

      <FD timeout="10000" max_tries="4"/>

      <VERIFY_SUSPECT timeout="5500" down_thread="false" up_thread="false"/>

      <pbcast.NAKACK gc_lag="100" retransmit_timeout="600,1200,2400,4800"/>

      <pbcast.STABLE stability_delay="1000" desired_avg_gossip="20000" down_thread="false" max_bytes="0" up_thread="false"/>

      <pbcast.GMS print_local_addr="true" join_timeout="5000" join_retry_timeout="2000" shun="true"/>

      </config>

      Before your Fix: Version 2.2.8

      Average receiving time(in milliseconds): 1106

      Max reciving time(in milliseconds: 3266

      Min reciving time(in milliseconds: 0

      After your Fix: Latest from Head

      Average receiving time(in milliseconds): 342

      Max reciving time(in milliseconds: 1250

      Min reciving time(in milliseconds: 0

      <config>

      <TCP start_port="7800" bind_addr="192.168.0.57" loopback="true"/>

      <TCPPING timeout="3000" initial_hosts="192.168.0.57[7800]" port_range="3" num_initial_members="3"/>

      <FD timeout="10000" max_tries="4"/>

      <VERIFY_SUSPECT timeout="5500" down_thread="false" up_thread="false"/>

      <pbcast.NAKACK gc_lag="100" retransmit_timeout="600,1200,2400,4800"/>

      <pbcast.STABLE stability_delay="1000" desired_avg_gossip="20000" down_thread="false" max_bytes="0" up_thread="false"/>

      <pbcast.GMS print_local_addr="true" join_timeout="5000" join_retry_timeout="2000" shun="true"/>

      </config>

      Before your Fix: Version 2.2.8

      Average receiving time(in milliseconds): 36

      Max reciving time(in milliseconds: 219

      Min reciving time(in milliseconds: 0

      After your Fix: Latest from Head

      Average receiving time(in milliseconds): 29

      Max reciving time(in milliseconds: 109

      Min reciving time(in milliseconds: 0

      Attachments

        Activity

          People

            rhn-engineering-bban Bela Ban
            rhn-engineering-bban Bela Ban
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified