I am focusing and playing around with the METATILE parameter and get performance of 1 tile request :-
METATILE(16) - 10 secs METATILE(8) - 3.5 secs METATILE(4) - 1.5 secs METATILE(2) - 0.6 secs So it seems the best performance for rendering a NEW TILE is to use the minimum metatile size of 2 (default is 8). But, once it is cached, does that mean a Metatile size of 2 is not as fast as a Metatile of 16 when fetching a CACHED TILE or just that the disk storage is not so efficient? On Thu, Jan 12, 2012 at 11:49 AM, Martin Koppenhoefer < dieterdre...@gmail.com> wrote: > 2012/1/12 Jason Lee <jaslee...@gmail.com>: > > Thanks for the tip Frederik, > > I enabled Postgres logging and the SQL selects are quite fast (under > > 1000ms). I am guessing the load maybe on the tile rendering and tile > cutting > > maybe. > > > You will have to add the time of those single requests (for every > db-based mapnik-layer a request is issued) to get the total selection > time for a (meta) tile. > > cheers, > Martin >
_______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
