Martin

It is probably not Blockbook itself but Rocksdb, who is taking memory. This is exactly why this issue exists, we are not able to control memory usage of Rocksdb as...

16 GB RAM should be more than enough for Litecoin. Is it really a memory problem? Have you tried to run the inital import with settings mentioned in [this](https://github.com/trezor/blockbook/issues/43#issuecomment-430250645) comment?...

Hi, the workers are in the same process as goroutines, you cannot see them using `ps`.

There is now an option to build Blockbook with TCMalloc, see https://github.com/trezor/blockbook/commit/212b767925663eeb93715961a89b8efcbab3713d and in the [documentation](docs/build.md). Unfortunately, the tests we have done do not show any advantage of using TCMalloc....

Hi, with the bulk import, the memory required is at least 32GB and will take about 24-36hours. Without the bulk import (with the setting `-workers=1`), the required memory is about...

Hi, thank you for your proposal. My comments: 1) Crashing or making the DB inconsistent under load: we have never observed this behavior and since Blockbook uses RocksDB transactions to...

One cannot see your setup from the error description but it looks like the backend is not synchronized correctly (or Blockbook is connecting to wrong backend).

It is planned for the next release, be patient, please.

@dylanseago Hi, do you know what exactly is the reason for https://github.com/trezor/blockbook/issues/665 in your configuration? We do not observe this problem. And in general, we are reluctant to accept PRs...

Hi, the `txs` field always contains the total number of transactions.