Improve performance of overpass.osmcha.org and / or enable switching overpass providers

[tordans]

I see in my network tab that it takes 11 seconds for the overpass request to finish before I can see the changes.
It looks like the overpass server at overpass.osmcha.org is overloaded.

A kind of workaround would be to allow to change the servers in the frontend.

But of course a better way would be to have a server that can handle the load.
I read in https://www.openstreetmap.org/user/wille/diary/403465#comment56731 that this is a know problem.

We need to do more work on it, as the performance of the API is not good yet. We had to reduce the configuration of the database, so the costs can fit the OpenStreetMap US budget.

Are there any updates on it? (Assuming this quote talks about the overpass server.)

[mmd-osm]

Assuming this quote talks about the overpass server

I don’t think this particular quote has anything to do with overpass, since none of the following applies:

We have also made some optimizations on the database, for example evaluating the indexes and changing some SQL queries to be more efficient.

On the topic of Overpass performance, this is likely a side effect of #719 (lack of caching causes all requests to hit Overpass in the end)

Then the Overpass instance used by Osmcha is about two years old. No compression for response message in place.
I tried a few queries on overpass-api.de, and they were much faster there.