Rather than shuffle the order of jobs in the queue to try not to overload the server, is it possible to look at this from another angle?
Could perhaps the server stop giving out new requests when active requests + number of requests in update queue > ~95% of maximum upload queue? That way the upload queue is unlikely to fill completely, which seems to be where the problems are at the moment (I've been trying to upload the same result for about 8 hours now, and the intervals between retries are somewhere about 600 seconds). I'm not sure what's involved with implementing such a change though. So much of [EMAIL PROTECTED] is still a mystery. Ed _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
