joto left a comment (osm2pgsql-dev/osm2pgsql#2482)

I collected more than 24h of changes, about 1.3 million tiles to expire. The 
processing needed about 14 minutes. So it looks like this does work even for 
longer update intervals. At some point, say with weekly updates or so, it will 
probably make more sense to drop the table and re-calculate everything, because 
we know this only needs 20 minutes.

One other thing to take into account: Because we are merging only roads that 
have a name or ref, it could make sense to have two "raw" tables, on with 
"mergeable roads", one with all others. That should speed up processing. And it 
could help when using the data, because you can then use `UNION ALL` to merge 
the "non-mergeable roads" with either the "mergeable roads" or the "merged 
roads" as needed. But that's all details that need to be tested in the real 
world. If the whole thing just needs Lua/SQL and not C++ code, as I think, it 
becomes much easier to do different kinds of experiments like this.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/pull/2482#issuecomment-4766226535
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/pull/2482/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving

Reply via email to