Hi Michael and Simon,

Thanks for your replies.

What makes the same overpasa query work at one moment and timeout at another?

Is there a queue system with a max CPU allotted to each query process with a different cpu allocation based on server load?

I essentially do what you are saying by splitting the world into quadrants and looping through.... with a 5 minute delay between queries.

I don't actually make that many queries ~ 200 to get the world fountains...And I have no current plans to run the query more than once a day so for now it's more out of curiosity. ....

Thanks,

Stuart

On Thu, 9 Jan 2020, 20:56 michael spreng, <mailinglist@osm.datendelphin.net> wrote:

Hi Stuart

To add to Simons answer, maybe these graphs are a bit more enlightening:
http://overpass-api.de/munin/other-day.html to see the load of the server.

You can also query your own status at https://overpass-api.de/api/status

Generally, you get better success getting a slot on an overcrowded
server by making smaller queries. So maybe divide your query into square
bboxes and wait some seconds in between until you are granted a new slot.

Hope that helps
Michael

_______________________________________________
talk-ch mailing list
talk-ch@openstreetmap.ch
http://lists.openstreetmap.ch/mailman/listinfo/talk-ch