Conversation
prawns/balances/src/processor.ts
Outdated
| await ctx.store.save(mergeAccounts(models.accounts, existingAccounts)); | ||
|
|
||
| await Promise.all([ | ||
| ctx.store.save(models.transfers), |
There was a problem hiding this comment.
I think save takes an array... so I think you can do a single save with all models
There was a problem hiding this comment.
that is an array, but I was a bit nervous about sending an array of different model types! I'll give it a go
There was a problem hiding this comment.
It definitely worked pre-firesquid as I did it in governance somewhere.
There was a problem hiding this comment.
Updated, I've left accounts above as it's essential they go in first
| ): SubstrateBalanceAccount { | ||
| // existing in this batch only... db check & merge done at the end | ||
| const existingAccountIndex = models.findIndex((acc) => acc.id === id); | ||
|
|
There was a problem hiding this comment.
Bit picky... but feel like this would be easier to follow if the condition between creating a model and changing it were separated. Something like
let model = models[existingAccountIndex];
if (!model) {
model = new SubstrateBalanceAccount({
id,
publicKey,
network,
symbol,
decimals,
firstBalanceChangeEventDate: date,
firstBalanceChangeEventBlockNumber: blockNumber,
lastBalanceChangeEventDate: date,
lastBalanceChangeEventBlockNumber: blockNumber,
totalTransfers: 0,
totalBalanceChangeEvents: 0,
});
models.push(model);
}
model.lastBalanceChangeEventDate = date;
model.lastBalanceChangeEventBlockNumber =
blockNumber;
model.totalBalanceChangeEvents += 1;
if (isTransfer) {
model.totalTransfers += 1;
}
There was a problem hiding this comment.
That's easier to read, updated
| async function processEvent(params: EventProcessorParams) { | ||
| switch (params.item.name) { | ||
| case 'Balances.Transfer': { | ||
| const { from, to, amount } = getBalancesTransferEvent( | ||
| params.ctx, | ||
| params.item.event, | ||
| network | ||
| ); | ||
| handleBalanceChange({ | ||
| eventType: SubstrateBalanceChangeEventType.BalancesTransfer, | ||
| processorParams: params, | ||
| eventParams: { | ||
| amount, | ||
| account: to, | ||
| from, | ||
| }, | ||
| }); | ||
| break; | ||
| } |
There was a problem hiding this comment.
I just wish there was a better solution for this switch statement :D But don't have a better one
3 participants
The batch processor looks good:
Without it (fire squid still though):
28.7mins
1723.42secs
With it:
1.31mins
78.79secs
Data processed:
Network: polkadot
Squid: balances
Start block: 10,000,000
End block: 10,100,100
According to this we can index all of balances for a network in a couple of hours. I think the bottle neck is DB write speed, but it's plenty fast enough.