`concurrency` Problems caused by concurrency

near / near-indexer-for-explorer

Watch NEAR network and store all the data from NEAR blockchain to PostgreSQL database

https://near-indexers.io/docs/projects/near-indexer-for-explorer

GNU General Public License v3.0

123 stars 56 forks source link

`concurrency` Problems caused by concurrency #184

Closed rayn316 closed 2 years ago

rayn316 commented 2 years ago

When I use the default concurrency value of 100, starting at the block height of 4050,000, it is easy to get stuck in the progress and the speed becomes very slow. When I change to single-threaded 1, then the block can be analyzed smoothly, and there will be no slowness.

rayn316 commented 2 years ago

So I suggest to modify the tutorial and set it to 1 Multithreading is only used to test data integrity

khorolets commented 2 years ago

Thanks for the report. Yeah, it's suboptimal at the moment to try to run Indexer for Explorer in multi-threading mode. We're trying to figure out how to enable a fair multi-thread. I'd keep this issue as a tracking one.

So I suggest to modify the tutorial and set it to 1 Feel free to create a PR :)