Andrii

> I'll try with rocksdb and see if it makes a difference in size - [@x3c41a](https://github.com/x3c41a) which db was your local node running with? I was not using local node...

So I: - spun up a local network using the command above (with paritydb), - generated pre-fetched db with `npx @acala-network/chopsticks@latest fetch-storages '0x' --endpoint=ws://localhost:9944 --config=configs/polkadot.yml` - and tried to fetch...

Same thing happens when the db is populated with this command: `npx @acala-network/chopsticks@latest fetch-storages Balances System --endpoint=ws://localhost:9944 --config=configs/polkadot.yml ` I'll try rocksdb now UPD: same problem

I was thinking about potential ways to understand why chopsticks does not use pre-fetched keys and quires the db. The problem is either with [0] db prefetch -- it might...

The problem is a bit different. When I - pre-fetch storage with one of the commands above, let's say: `npx @acala-network/chopsticks@latest --config=configs/polkadot.yml ` and config: ``` endpoint: ws://localhost:9944 mock-signature-host: true...

Thanks for the input @ermalkaleci ! Could you elaborate on key ordering? I am not sure if I get this right. maybe some code reference? Is there a workaround to...

> I don't see any block specified in previous comments so if you run those scripts multiple times you will end up fetching state for different blocks, that might be...

> > let sysEntries = await polkadot.api.query.system.account.entries(); > > this here will get all keys from RPC and this looks like RPC rate limiting disconnecting you. Correct my logic: -...

> Chopsticks uses db to cache the values, finding next key will always hit RPC Don't I find all the keys during the pre-fetch? I am trying to understand what...

> Unfortunately no, Chopsticks needs an RPC or genesis to run. The db is a caching layer so you don't hit RPC to read state all the time. Chopsticks cannot...