Replies: 1 comment
-
Closing this discussion as #3043 has evolved out of it |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, we do not have any benchmarks that outline how our SDK performs in Node or Browser environments. At the offsite we discussed some possible code paths and flows that would be useful for us to benchmark given the core functionality of our SDK.
On the performance testing branch I wrote a few benchmark tests such as:
These can be found in the account.bench.ts , wallet.bench.ts and crypto.bench.ts respectively.
That branch also utilizes a tool called clinic.js to profile and pinpoint performance issues in Node environments.
Ideally we would like to derive some benchmarks, and then run our test suite against that pre-merge so that we can detect regressions, but we could have these running post-merge on master as a start. This will give us an idea of what consumers should expect when interacting with our SDK and potentially identify bottlenecks and optimizations.
Beta Was this translation helpful? Give feedback.
All reactions