-
Notifications
You must be signed in to change notification settings - Fork 10
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
Support batched transactions #223
Changes from all commits
f5d8ac3
5a767fe
1491478
ca9197b
0fc58f2
4b169c2
399133a
e2db84a
3de63ad
5de73d7
583a421
a84996a
191d667
1910040
d416988
20c7e2d
1da46e3
faaf3ed
a42429b
81cb1d4
e0b6384
6b66045
5c8ffb5
e210e0f
c529aee
d6117a9
4c391ca
5a910a3
08ddfaf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -64,8 +64,7 @@ type ReceiptIndexer interface { | |
// GetByBlockHeight returns the receipt for the block height. | ||
// Expected errors: | ||
// - errors.NotFound if the receipt is not found | ||
// TODO right now one transaction per block, but this might change in future so the API needs to be updated. | ||
GetByBlockHeight(height *big.Int) (*gethTypes.Receipt, error) | ||
GetByBlockHeight(height *big.Int) ([]*gethTypes.Receipt, error) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ensure consistent error handling for the The |
||
|
||
// BloomsForBlockRange returns slice of bloom values and a slice of block heights | ||
// corresponding to each item in the bloom slice. It only matches the blooms between | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Optimize log filtering with concurrent processing.
The current implementation of log filtering in the
RangeFilter
class processes receipts sequentially. Given that log filtering can be a CPU-intensive operation, especially with a large number of receipts, consider implementing concurrent processing of receipts to improve performance. This could involve using worker pools or parallel processing techniques to handle multiple receipts simultaneously.