pnorman
commented
3 years ago I made a few changes that should fix most of this
- evaluated label collisions for place points server-side, leaving final placements and collisions to the client. There are now never more than about 250 possible place points in a tile.
- Pushed landuse and vegetation one zoom later. This isn't ideal, but is needed for now.
- Removed non-essential attributes from most layers
- Used ST_Collect to turn lots of polygons into one large multipolygon, reducing the number of objects to be rendered.
I also moved the rendering to https://took.paulnorman.ca/build/mapbox-gl.html to start working on integration with a minutely updated DB.
Testing with Chrome on Windows shows total memory increase from loading the site and panning of about 500mb.
At z7 and z8 in areas with lots of landcover and roads, the rendering bogs down when scrolling around and zooming in well-mapped areas, for example France or the Netherlands. This was mentioned on the mailing list back in May but the current implementation at https://pnorman.dev.openstreetmap.org/cartographic/ still has this problem
https://pnorman.dev.openstreetmap.org/cartographic/mapbox-gl.html#7/49.518/3.728 and https://pnorman.dev.openstreetmap.org/cartographic/mapbox-gl.html#8/52.023/5.778
I’m viewing this on Safari and Chrome on a 2015 Macbook Pro with 16 GB RAM, 2.2 GHz Intel Core i7 processor.
Safari warns me that “this web page is using significant memory. Closing it may improve the performance of your Mac”. Usually the warning apppears after about a minute of scrolling / zooming.
On Chrome it looks to be using about 3 GB of RAM, if I’m looking at the processes correctly in the Activity Monitor app (Google Chrome Helper GPU = 1.6 GB, Google Chrome Helper Renderer = 1.5 GB and these drop off when the window is closed). CPU usage can be >300%