"Ævar Arnfjörð Bjarmason" <[email protected]> writes: > When I render areas that aren't cityscape I note that most of the time > to render each tile is being spent on the post-optimization and > compression of the generated png file. If I look at the generated .png > file I find that up to 95% of them share the same md5sum.
I would be surprised if so many tiles that are actually not empty should have the same content. Were you looking at empty tiles? > > If the PNG optimization and compression routines in Tileset.pm kept a > record of the previous byte size of generated tiles (as reported by > stat()) and if they matched ran md5sum() on them and if that matched > simply copied over the old previously optimized tile instead of doing > the work again a speedup could be gained. Large amounts of the tiles > on the planet probably have some duplicate parts. I guess you were looking at empty tiles (67 or 69 bytes). Empty tiles are not optimized. In fact, they are never written to disc. When the client finds during tile splitting that a tile is empty it throws the tile away and copies emptyland.png or emptysea.png from the client's root directory. Those are actually 1 pixel PNGs with 67 respective 69 bytes size. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
![Re: [Tilesathome] Potential t@h optimization: Re-use the optimized .png image](/search?l=tilesathome@openstreetmap.org&q=subject:%22Re%5C%3A+%5C%5BTilesathome%5C%5D+Potential+t%40h+optimization%5C%3A+Re%5C-use+the+optimized%09.png+image%22&o=newest){kind=link}
