On 26/01/15 12:00, Paul Norman wrote:
On 1/26/2015 2:58 AM, Dave F. wrote:
I don't know when it was last reviewed, but does this error have bit
of a sensitive trigger? Has the server that runs the process been
upgraded so it can handle a greater number of requests? If so, could
the error's cut in point be relaxed?
The thresholds for each server have been adjusted multiple times and
will probably continue to be so. Even if the load cutoff is increased
there will be times when individual render requests are rejected for a
few days in a row - stylesheet updates being the main one. It is
considered more important to update the map rendering than to do a
custom render. Personally I don't have many problems generating a custom
render from osm.org, but I'm on a different timezone and keep different
hours, which makes it hard to compare. I also get directed to a
different server much of the time.
I suspect main difference is that you're hitting orm and Dave is hitting
yevaud. There is an ops ticket open for our efforts to get yevaud
upgraded to improve the performance:
https://github.com/openstreetmap/operations/issues/5
Tom
--
Tom Hughes (t...@compton.nu)
http://compton.nu/
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
