Uploaded image for project: 'Fabric'
  1. Fabric
  2. FAB-17519

Discovery service performance issue

    XMLWordPrintable

Details

    • Bug
    • Status: To Do
    • Medium
    • Resolution: Unresolved
    • v1.4.4, v1.4.5
    • v2.x
    • fabric-gossip

    Description

      We run several channels with 3 chaincodes having endorsement policies like

      ORG1 & OUTOF(7, ORG2..ORG14)

      ORG1 has two endorsing peers, others have single.

       

      Transactions are produced by gateway software fabric-sdk-go v1.0.0-beta1 with dynamic discovery on.

       At some point of time peer process start consuming all cpu . Load doesn’t end at turning off of gateway software of that org. CPU load spike doesn't start immediately. 

       Attaching trace of peer process during this problem.

       Probably Discovery shouldn’t try to build all possible combinations of endorsing peers and just return N variants to save CPU and bandwidth?

       

       

      Attachments

        1. 1.4.6-pprof.pdf
          34 kB
        2. 1.4.6-pprof.svg
          58 kB
        3. trace.svg
          116 kB

        Activity

          People

            Unassigned Unassigned
            mplisov Mikhail Plisov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: