Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5198

Clustering performance regression

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 10.0.0.CR1
    • 10.0.0.Beta1
    • Clustering
    • None

    Description

      Our clustering stress tests show huge performance drop of 7.0.0.DR8 bits compared to 6.4.0 bits.

      Compare these results:

      stress-heavyread-session-repl-sync
      7.0.0.DR8: throughput + response times
      6.4.0.GA: throughput + response times

      Jenkins runs (server configs + logs can be found here):
      7.0.0.DR8: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-stress-heavyread-session-repl-sync_noperf21/2/
      6.4.0.GA: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-stress-heavyread-session-repl-sync_noperf21/1/

      One can observe that when using 7.0.0.DR8 bits, throughput reaches a threshold of approximately 6000 TPS. This happens in each test using REPL-SYNC cache, for example:

      stress-session-repl-sync
      7.0.0.DR8: throughput + response times
      6.4.0.GA: throughput + response times

      All tests use a 4-node EAP cluster and 5 nodes that generate load. Adding another node to the EAP cluster, the threshold is lowered to 5200 TPS and the max. response time raises, see:

      stress-heavyread-session-repl-sync with 5-node cluster
      7.0.0.DR8: throughput + response times

      Most of the other scenarios indicate performance regression as well.

      stress-session-dist-sync
      7.0.0.DR8: throughput + response times
      6.4.0.GA: throughput + response times

      stress-session-repl-async
      7.0.0.DR8: throughput + response times
      6.4.0.GA: throughput + response times

      This issue is related to https://issues.jboss.org/browse/JBEAP-768

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-858 Clustering performance regression

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5617 JGroups thread pool properties are never applied

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5581 Routing cache should always use REPL

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5591 Client mappings cache should always use REPL

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              mvinkler1@redhat.com Michal Vinkler
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: