Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Cache a pointer to account_statistics_object in account object? #1095
We've split account data into
Every time when looking for an account's statistics object after we already find the account object, we search from the root of the index, which is expensive especially when the index is large.
Since the address of the objects won't change after the block that they're created become irreversible, can we cache address of each other in the objects? For example, add an
Same thing can be done for
At this time I think for the sake of stability we should avoid fiddling with pointers.
@jmjatlanta there isn't really a "normal case" for undo_db - incoming transactions are applied with an undo session that is rolled back before the next incoming block is applied. I. e. it is rolled back about as often as not. During replay undo_db is disabled anyway.