[OSM-dev] TIGER data show OSM getting slower??

Dermot McNally dermotm at gmail.com
Mon Sep 17 00:41:42 BST 2007

On 16/09/2007, Frederik Ramm <frederik at remote.org> wrote:

> I don't know if this may be a cause but I have, in the past two weeks
> or so, started rendering those parts of the world for tiles at home that
> hadn't yet been rendered with Osmarender 5. I didn't think that would

I don't know if we can consider this a cause for the slowdown, but it
might explain a further phenomenon - over the past week or so, I've
noticed that my render requests for areas I've recently altered just
don't get processed, while the tiles at home pending queue just gets
longer and longer. I assumed the cause was either slow API (tiles
clients giving up and the render request going around the loop again),
teething problems with osmarender5 or some combination of the two.

However, it could just as easily be down to sudden enlargement of the
queue, such as might result from what you describe. It might even be
related to the TIGER import, if those tiles are triggering render

My instinct is that we shouldn't trigger any more tile re-renders than
we have to until the rendering queue returns to a sane state. (Sanity
here is defined as "not growing").


More information about the dev mailing list