Stefan Stojanović

I have mentioned this in my issue also https://github.com/aws/amazon-managed-grafana-roadmap/issues/97 Please ! this is causing weird workarounds. In my opinion, its a bigger security risk to go through workarounds then have...

we've increased it before to `--db.read.concurency=16384` but removed the flag as there was no significant results from that I will for reference do it on 9000 and bring the results...

fyi still observing spikes with 9000 on `db.read.concurrency` Here is pprof CPU  MEM 

good to know its spotted would you suggest using any workarounds in the meantime until this gets resolved ? can we downgrade nodes before "ReOpen" was introduced ?

We did a node upgrade to 2.60.6 on 28th of August, so It doesn't look like its related to bumping up the version. I can't say if its happening on...

will test if the issue persists and get back in here

Sorry guys, this takes longer then anticipated to test since the underlying base image also changed so we gotta incorporate that . Will have some info for this by EOW

Hey guys We've basically tried to make 2.60.10 reduce the latency for across regions and here is what we found out and what we are battling against currently: - A...

thanks for suggestions and ideas Alex Dedicating time to the first point currently. Got no Polygon nodes with "normal" ledger sizes all increased up to 9TBs of data. For Ethereum,...

We've noticed improvments when replacing Ethereum ledgers, still not at its best comparable to geth, but its a lot better  wondering what causes these bloated ledgers ? is it...