[Tile-serving] [osm2pgsql-dev/osm2pgsql] Practices to handle tile expiration (Discussion #2495)

[Jochen Topf]

It is quite unusual to have different sets of data for each different zoom level. Usually for something like highways you have two or three different tables, one with all data for higher zoom levels, one for middle zoom levels and one for low zoom levels if needed. The tables for mid zoom levels don't need a lot of the data (for instance you usually don't render oneway arrows at that level) so they might contain aggregated and simplified data anyway for faster rendering. So the tables are quite different anyway and it makes sense to do expire on the table level.

Because tables for lower zoom levels are so much smaller than the tables with complete data, updating and rendering those tables is much much faster in practice, having many tables isn't a problem.

You should do expire after each data update run, doing this every second doesn't improve anything, because you get new data at most once per minute.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2495#discussioncomment-17574191
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/repo-discussions/2495/comments/17574191 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20260708/24117e15/attachment.htm>