[Tile-serving] [openstreetmap/osm2pgsql] Tile Expiry Performance (#946)

[intergalacticdata]

> Applying a weekly diff and creating expiry list for z19 is one of them. I wouldn't expect the expiry to be optimised for that. A daily diff at z16 should be doable though.

The formatting was not the clearest (I apologize), but please note this test:

DAILY changeset using Debian backport to stretch (0.96):
-=-=-=-
As above, using -e10-16.

22 hours spent processing a 24 hour changeset and still importing new relations. It's 35GB into swap, with osm2pgsql claiming 89% of the memory usage.

I realize there is a large difference between zoom level 19 and 10-16, but I assume it should take significantly less RAM/CPU for 10-16.


-- 
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/osm2pgsql/issues/946#issuecomment-521422999
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20190814/68896fe5/attachment.html>