>> Yes, i already adopted it for out multi-style-environment on cassini and >> placed it at [1], but on cassini it was very slow with this much styles. > > Do you know what the bottle neck was? Was it DB access to generate the > list of tiles, cpu speed running the ruby script, or filesystem > performance to touch a huge number of files? I guess it was the filesystem, because the script only queries the DB once, no matter how much styles you'll expire.
> Presumably ptolemy is > running a different filesystem, so the latter might behave quite > differently. At first we can just touch the global planet-import > timestamp though every couple of days expiring all tiles at once while > we get everything else running reliably. I suspect there are still some > optimizations possible that might be sufficient, but we will need to see > what performance is like on ptolemy first. Yay, we'll to this. Maybe it would be enough to touch the lower 4 or 5 zoom levels on a per-minute or per-5-minute basis and leave the rest for a weekly expire-all event. Peter _______________________________________________ Maps-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/maps-l
