Add post accounts state data to geyser transactions #5114
+110
−25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Subscribing to both transactions and accounts and then synchronizing their updates is a major pain when you need all the data. Not only is it difficult to implement correctly, but it also introduces excessive redundant allocations and increases system latency. This PR adds post-transaction account states to transaction notifications.
Summary of Changes
Added
ReplicaTransactionInfoV3
with a new fieldpost_accounts_states
, which has the type:Vec<(&Pubkey, TxnReplicaAccountInfo<'a>)>
.TxnReplicaAccountInfo<'a>
contains account data without the pubkey field.This data is passed from
loaded_accounts: Vec<(Pubkey, AccountSharedData)>
, which was previously just dropped afterCommittedTransaction
was createdConcerns
There should be no performance impact or additional allocations but I aimed to make minimal changes and follow the existing code style in
geyser-plugin-interface
. To achieve this, I avoided importingAccountSharedData
intogeyser-plugin-interface
(because it adds new dependency togeyser-plugin-interface
), leading to a single instance where an additional redundant allocation occurs:This additional allocation could be avoided by importing
AccountSharedData
andPubkey
intogeyser-plugin-interface
and changingpost_accounts_states
to use owned types.