-
Notifications
You must be signed in to change notification settings - Fork 47
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
added function name for pool transactions #1425
base: development
Are you sure you want to change the base?
Conversation
k6 load testing comparison.
Legend: Avg - Average Response Time, Max - Maximum Response Time, 90 - 90th Percentile, 95 - 95th Percentile |
@@ -105,6 +109,11 @@ export class PoolService { | |||
transaction.receiverShard = AddressUtils.computeShard(AddressUtils.bech32Decode(transaction.receiver), shardCount); | |||
} | |||
|
|||
const metadata = await this.transactionActionService.getTransactionMetadata(this.poolTransactionToTransaction(transaction), false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In our Python implementation, we have a small issue with parsing some badly-formatted transactions. If the issue exists in the JS implementation, as well, a tiny failure might make the whole request fail, I think. Perhaps have a more pessimistic approach?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additionally, maybe we should benchmark this? Or is the logic applied for a mere page of transactions, not all?
If applied on all currently in pool, we might have a small performance issue?
💭
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a tiny failure might make the whole request fail, I think
no, if the decoding fails, it will just returned undefined
, therefore not applying the function name
regarding the performance impact, it is ok since we cache the entire pool so the processing only happens once
Add also the |
Reasoning
Proposed Changes
How to test
/transaction/pool
should contain the transactions functions