Uploaded image for project: 'Indy SDK'
  1. Indy SDK
  2. IS-1066

Investigate LibIndy to identify reasons for slow proof generation

    XMLWordPrintable

Details

    • Task
    • Status: Complete
    • Highest
    • Resolution: Done
    • None
    • 1.6.8
    • None

    Description

      Proof generation should take less than 2 seconds from the SDK.

      Proof generation in applications built by the Evernym engineering team is taking much longer. We are seeing the problem in both Android and IOS environments using Evernym's Connect.Me.

      We should test that the delays are not in the time necessary for the SDK to respond.

      Acceptance Criteria
      Test proof generation in the following environment:

      • A proof with 10 attributes
      • Using 3 different credential definitions from 3 different trust anchors
      • In Android environment (using the Android Wrapper)
      • At the LibIndy layer
        Report the distribution of response times.

      Notes

      • We start with the Android layer because we have more reports of slowness from that layer. Investigating IOS would also be useful.

      Reference issues (internal to Evernym):
      CM-2070 - Connect.Me shouldn't be dependent on ledger connectivity for presenting proofs
      CM-2072 - Sending a proof should take less than 2 seconds

      Attachments

        Issue Links

          Activity

            People

              sergey.minaev Sergey Minaev
              sergey.minaev Sergey Minaev
              Sergey Minaev, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: