moneroexamples

Same issue as here with a solution: https://github.com/moneroexamples/onion-monero-blockchain-explorer/issues/169 Can start monero daemon with smaller concurrency using `--max-concurrency 60` option. This should help.

Thanks. Will look into that. I had this issue in OpenMonero, but it was because OM uses a lot of threads. It was fixed by changing OM architecture. Explorer does...

Does the issue occur each time you start xmrblocks, or from time to time?

`concurrency,c` option was added into `devel` branch. With this you can limit how many threads are used to server http requrets. By default it is based on your hardware, and...

For now I don't know whey those stale readers originate from. As a temporary solution you could maybe use `cron` to schedule periodic cleanup of these readers using `mdb_stat`.

@Gingeropolous Could you provide the argument list how you execute the explorer? I will try to replicate the issue by putting some load on my localhost using jmeter.

T.L.D.R: Switch off caching, i.e., use `--enable-tx-cache 0 --enable-block-cache 0 `, and check if it helps. I tested few scenarios using jmeter, and I found an issue leading to max...

@Gingeropolous The issue persists? I though that removing cashes from the explorer helped, as this is what I identified as a cause of the problem in my previews tests.

The explorer was causing this issue, as explained here https://github.com/moneroexamples/onion-monero-blockchain-explorer/issues/178#issuecomment-536166666 But I thought the issue was resolved. But maybe there is something new in the explorer that is causing the...

Did it start happening with new changes in the explorer introduced for the upcoming HF?