[Tile-serving] [openstreetmap/mod_tile] Update render queue limits (#152)

[mmd]

I'm a bit confused by this proposed change. There are basically 5 different queue categories, which are being fetched by `request_queue_fetch_request` in the following order: 

1. Priority Request Queue, 
2. Request Queue,
3. Low Priority Request Queue, 
4. Dirty Queue, and 
5. Bulk Request queue. 

As long as there are queue entries in a higher class, they will be processed first. (I wonder why this doesn't lead to starvation issue, but that's another issue).

To my understanding, changing the `DIRTY_LIMIT` will **only** affect entries in category (4), that is the Dirty Queue. However, this queue seems pretty empty most of the time anyway: [munin link](https://munin.openstreetmap.org/static/dynazoom.html?plugin_name=openstreetmap%2Fyevaud.openstreetmap%2Frenderd_processed&start_iso8601=2017-11-01T07%3A34%3A44%2B0100&stop_iso8601=2017-12-02T01%3A41%3A13%2B0100&start_epoch=1509518084&stop_epoch=1512175273&lower_limit=&upper_limit=&size_x=800&size_y=400&cgiurl_graph=%2Fmunin-cgi%2Fmunin-cgi-graph)

Isn't this queue only relevant, if someone adds `/dirty` to an URL to manually trigger a re-rendering of a tile?



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/mod_tile/pull/152#issuecomment-348778256
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20171203/3e60de18/attachment.html>