You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #5086 we improved performance of the ClaimableBalancesChangeProcessor by using COPY to bulk insert claimable balance rows. We should use COPY to improve the performance of all the remaining change processors.
Most of the change processors combine new ledger entries and updates of existing ledger entries into a single list which is then upserted into the DB. We should change this workflow so that we handle new ledger entries separately from updating existing ledger entries because we can bulk insert new ledger entries efficiently with COPY.
The claimable balance change processor has already been taken care of in #5086 and the asset stats processor is still in flux because of #5033 . So we should implement the COPY optimization on the following remaining change processors:
I anticipate that once COPY is used in all the change processors, ingesting from the history archives will be significantly faster, which means that state rebuilds will much faster than before.
The text was updated successfully, but these errors were encountered:
In #5086 we improved performance of the ClaimableBalancesChangeProcessor by using COPY to bulk insert claimable balance rows. We should use COPY to improve the performance of all the remaining change processors.
Most of the change processors combine new ledger entries and updates of existing ledger entries into a single list which is then upserted into the DB. We should change this workflow so that we handle new ledger entries separately from updating existing ledger entries because we can bulk insert new ledger entries efficiently with COPY.
The claimable balance change processor has already been taken care of in #5086 and the asset stats processor is still in flux because of #5033 . So we should implement the COPY optimization on the following remaining change processors:
I anticipate that once COPY is used in all the change processors, ingesting from the history archives will be significantly faster, which means that state rebuilds will much faster than before.
The text was updated successfully, but these errors were encountered: