-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Askar unusably slow for mediator #1621
Comments
FYI — when we switched to Askar we got a significant boost in performance, and other benchmarks have shown Askar to be much faster and more stable than the IndySDK — especially under load. Thanks for the easy reproduction instructions — we’ll have to take a look at this. It is curious... |
Note that we were using an ACA-Py-based mediator, so we’re not comparing apples to apples in my note. |
We're using Askar on mobile side without issue. The above is a js mediator running in Node... |
This is related to a known performance issue in As a result, we now require at least node 18, and for that reason I've created #1622 to update It would be great if you can re-check from that branch or wait a bit until it is merged to main. |
The doc says that IndySDK support will be removed soon, but Askar is currently unusably slow for mediator.
This is evidenced by doing the following:
Run the sample mediator using indy:
docker build -t aries-framework-javascript .
docker compose -f docker/docker-compose-mediators up
curl "http://localhost:3001/invitation?"
, it returns in millisecondsNow run a similar mediator, simply using using askar in lieu of indy:
docker build -t aries-framework-javascript .
docker compose -f docker/docker-compose-mediators up
curl "http://localhost:3001/invitation?"
, it returns in several seconds instead of millisecondsThe above is a simple way to highlight the issue. We rolled out a mediator using askar in AWS and although we were able to get an invitation, any attempt to go further would trigger timeouts from the infrastructure. Switching back to Indy was the only way to solve the issue.
mediator.ts.zip
The text was updated successfully, but these errors were encountered: