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

Sarah Hoffmann notifications at github.com
Thu Aug 15 07:26:33 UTC 2019


> However, the influence on the total memory consumption is limited.

I'm not convinced you can prove that by looking at the  "Maximum resident set size". The "Maximum resident set size" is dominated by the memory-mapped flatnode file. It is not a really helpful measurement here because how much of it is resident is mostly determined by your available RAM size. 

However, @intergalacticdata's statement "While expiring tiles, [the memory usage] ballooned to >50GB before being killed." is similarly unhelpful. Newer versions of osm2pgsql always balloon like this because of the memory-mapped flatnode file. It is not an indicator of a memory leak, nor reason for being OOM-killed.

-- 
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-521544379
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20190815/d3a39242/attachment.html>


More information about the Tile-serving mailing list