-
Notifications
You must be signed in to change notification settings - Fork 5
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
Improve CCIP Contract Reader Querying #267
Conversation
Nice, not sure if you've seen this, but we actually have tickets to fix that for this sprint :D |
Well, a few tickets less for your sprint lol, I wanted to help with this and modifiers to see how is it to use the interface in practice |
d12f8fd
to
1048b34
Compare
1048b34
to
816f0fb
Compare
query.Comparator(consts.EventAttributeState, primitives.ValueComparator{ | ||
Value: 0, | ||
Operator: primitives.Gt, | ||
}), |
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.
Do we need to add postgres indexes for any of these datawords? If not, this could be very slow.
If we do need to add them, I wonder if there's a way we could add them only to chainlink-ccip
's fork but not to chainlink
?
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.
Yeah, probably will require some kind of detailed indexing. We have a task planned as performance work to go over all the DB queries we make from the ccipreader to better understand where we miss indexing/limits/paging etc
https://smartcontract-it.atlassian.net/browse/CCIP-3870
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.
However, in the long term we will probably need ChainReader's tables to be optimized for the specific products, for instance by
- by having custom indexes per product
- or having custom indexers and tables per product (for instance, the ability to dynamically index events in dedicated tables to limit the scans sizes)
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.
LGTM
816f0fb
to
9d45bb2
Compare
9d45bb2
to
0cf44c0
Compare
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.
LGTM
Integration tests are failing, that's because we need a updates to the contract reader config right? @ilija42 |
Have to merge core first |
|
related core PR smartcontractkit/chainlink#14935
Also relates to
CCIP-3866
and
CCIP-3865