On Sun, Oct 12, 2008 at 12:39, Milenko <[EMAIL PROTECTED]> wrote: > Also, this client version seems to ignore MaxComplexity and auto-generate > it's own. This is significantly lower (3819112 vs 8000000) on the working > client that what I had set in the past. This client has 2GB RAM and has > done tilesets at 6-7 million complexity before. Is this expected behaviour? > > -Jeremy
Looking at the code for _unstable (which is identical to stable at the moment, IIRC,) there's a function to recalibrate maxTilesetComplexity based on processing time. IMO, it's fixing one problem (people not having a good idea of where there complexity should be,) but causing others (I see a couple things I consider logic errors, and it ignores the fact that, for some of us, the bigger problem with complexity is available RAM and not available CPU cycles.) -- David J. Lynch [EMAIL PROTECTED] _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
