We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to benchmarks since nb #636 (revision 76b3a6d) fee estimation time increased from ~1.5s to 5-6s on empty Shelley wallet.
2020.9.11 (git revision: ffeca1d9e0f302111588c7890785051b6cc6b0da)
Should return not_enough_money right away.
not_enough_money
Takes 5-6s on nightly benchmarks. Note for comparison, it takes ~3-4s for 0.4% seq wallet.
0.4% seq wallet
(On my local machine I got ~3s for empty wallet, and ~1s on small wallet with funds)
The text was updated successfully, but these errors were encountered:
Looking at the commit history around 76b3a6d https://github.com/input-output-hk/cardano-wallet/commits/master?after=647632e17f1a4add822ab76aef01ba6772a7b813+244&branch=master,
it seems #2112 was merged just before, which seems suspicious
Sorry, something went wrong.
Resolved with #2348.
benchmark results on branch -> https://buildkite.com/input-output-hk/cardano-wallet-nightly/builds/743.
E.g.:
1-wallets-to-0.1: "estimateFeesTime":"8.950 ms" used to be = 9.975 s
100-wallets-to-0.01: "estimateFeesTime":"117.2 ms" used to be = 19.7 s
No branches or pull requests
Context
According to benchmarks since nb #636 (revision 76b3a6d) fee estimation time increased from ~1.5s to 5-6s on empty Shelley wallet.
2020.9.11 (git revision: ffeca1d9e0f302111588c7890785051b6cc6b0da)
Steps to Reproduce
Expected behavior
Should return
not_enough_money
right away.Actual behavior
Takes 5-6s on nightly benchmarks.
Note for comparison, it takes ~3-4s for
0.4% seq wallet
.(On my local machine I got ~3s for empty wallet, and ~1s on small wallet with funds)
Resolution
QA
The text was updated successfully, but these errors were encountered: