Gleb Vishnevsky

Tried to increase from 32 to 200, didn't help. Can you reproduce it on your side?

Tried to run with `—db.read.concurrency=5000`, seems to be working. Is it ok to run node with this setting? But still this is not quite the correct behavior of the program...

Eventually it stucked :( Even with this setting. First time I send ~5k requests and it responds successfully, then it stucks a second time I send them. So, I think...

Yes, I'm running a separated RPCDaemon, they are on the same machine, but in different containers. Tried to run with `--datadir` and it seems to be working, even with `db.read.concurrency=32`....

I see, thanks. What is known about this bug at the moment? Maybe a little more context, so I can try to check this out myself?

Could this be due to the fact that all go runtime threads are excluded? So there are no free threads for goroutines to process result form database. I can try...

Tried to run with default value (`max(10, GOMAXPROCS*2)`), `db.read.concurrency=2` and `db.read.concurrency=1` -- it still stucks.

@revitteth here is a test script https://github.com/kaikash/eth-call-test

It works very unpredictable, sometimes it stucks, sometimes it is not. Try increasing connection pool size (for me it stucks with 10 cons and 10k requests). Maybe this script is...

I've run unwind but it keeps halting. ```bash [INFO] [10-08|02:15:47.567] Commit cycle in=11.73884ms [INFO] [10-08|02:15:47.567] RPC Daemon notified of new headers from=15692870 to=15692931 header sending=76.941µs log sending=340ns [INFO] [10-08|02:15:47.567] [1/16...