I used the last rainy weekends to write a little python-tool[1] to bring the rendering processes for each day in a systematically order.
This ordering by geometrical position should reduce our load on harddiscs by reducing random-requests, better usage of disk-cache and preventing out-of-memory (during low-level rendering in different areas of the world at the same time).
The tools goes through all styles, from z=9 to z=15. It checks all metatile-files and looks to access-time and modify-time of each tile.
So the tile must have for re-rendering: *watched in the last 64 days *and must be older than a year (expiring process makes tiles much older). *in an specified area of the earth
This specified area depends on zoomlevel. z=15 will be renderd to 50% so it switch day by day from northern to southern hemissphere. z=14 will be renderd to 25% each day (NW,SW,NE,SE). this going further until z=9 where we render 1.56% and completed the world after 64 days. The system is so that the areas of lower zoomlevels are included in areas of higher zoomlevels. Lower zoomlevels cost us more and changes a harder to see, so I think an update-interval of 2 month for z=9 is acceptable.
At the end, I have a list of tiles that need a rerendering, I order this tiles by z-curve[2] and export it in an format that should be usable for tirex-batch (example: map=default z=15 x=5072 y=11208). This batch-process should starting at beginning of each night (lower server load). z=16-18 would be updated like now on request, because we have no problems there.
The scanning process of the meta-tiles needs on ptolemy nearly 1 hour. Perhaps somebody can check my code. I know that the tiles are not on ptolemy, so my scan is running over the network to willow (afaik), not optimal, but it seems acceptable.
In the moment we render 10.000 tiles in nearly 8hours[3], afterwards we should be much faster.
How can we bring the tool to live-system? Some ideas to optimize the tool/rendering process?
Greetings Kolossos
[1] public-sourcecode: http://toolserver.org/~osm/batchjob-creator/dir-search_source.php place of tool: /home/project/o/s/m/osm/tools/batchjob-creator/
[2]http://en.wikipedia.org/wiki/Z-order_%28curve%29
[3]tail -n -10000 tirex/var/log/jobs.log|less
Am 06.08.2011 14:44, schrieb Tim Alder:
How can we bring the tool to live-system?
Well, the obvious thing would be to put it into osm's $HOME/bin and create an entry into the crontab. It would be good to keep some logfiles about the actions performed, so we can check if it's really doing what we're expecting.
Peter
Hi,
won't # tirex-batch "bbox=<bounding box>" also work?
If this won't work I'd really like to try to help to improve the script, but when I login to the toolserver cluster I don't have an /osm/tiles folder. This makes me unable to test my changes. ("ssh ptolemy" fails with "connection closed" right after trying host based authentication; is this intended behavior?)
Julian
2011/8/6 Peter Körner osm-lists@mazdermind.de
Am 06.08.2011 14:44, schrieb Tim Alder:
How can we bring the tool to live-system?
Well, the obvious thing would be to put it into osm's $HOME/bin and create an entry into the crontab. It would be good to keep some logfiles about the actions performed, so we can check if it's really doing what we're expecting.
Peter
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l
Hello Julian, # tirex-batch "bbox=<bounding box>" would also work, but seems not useful, because we only want to update exsting tiles that are not up-to-date and are watched in last time.
If "ssh ptolemy" doesn't work for you it can be, that ptolemy only available for members of osm-mmp, but I'm not sure. What would be your ideas to improve the script?
Greetings Kolossos
Zitat von Julian Picht julian.picht@gmail.com:
Hi,
won't # tirex-batch "bbox=<bounding box>" also work? If this won't work I'd really like to try to help to improve the script, but when I login to the toolserver cluster I don't have an /osm/tiles folder. This makes me unable to test my changes. ("ssh ptolemy" fails with "connection closed" right after trying host based authentication; is this intended behavior?)
Julian
2011/8/6 Peter Körner osm-lists@mazdermind.de
Am 06.08.2011 14:44, schrieb Tim Alder:
How can we bring the tool to live-system?
Well, the obvious thing would be to put it into osm's $HOME/bin and create an entry into the crontab. It would be good to keep some logfiles about the actions performed, so we can check if it's really doing what we're expecting.
Peter
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l
Hello Kolossos,
actually I'm not quite sure if my ideas would really speed things up so I would really like to try them myself, and each one individually, on ptolemy or any other host that is able to access the metatile files. Who is able to tell me why I cannot login to ptolemy (username: haggi) or if it's possible to access the metatiles from some of the other host?
Julian
2011/8/8 Tim Alder tim.alder@s2002.tu-chemnitz.de
Hello Julian, # tirex-batch "bbox=<bounding box>" would also work, but seems not useful, because we only want to update exsting tiles that are not up-to-date and are watched in last time.
If "ssh ptolemy" doesn't work for you it can be, that ptolemy only available for members of osm-mmp, but I'm not sure. What would be your ideas to improve the script?
Greetings Kolossos
Zitat von Julian Picht julian.picht@gmail.com:
Hi,
won't # tirex-batch "bbox=<bounding box>" also work? If this won't work I'd really like to try to help to improve the script,
but
when I login to the toolserver cluster I don't have an /osm/tiles folder. This makes me unable to test my changes. ("ssh ptolemy" fails with "connection closed" right after trying host based authentication; is this intended behavior?)
Julian
2011/8/6 Peter Körner osm-lists@mazdermind.de
Am 06.08.2011 14:44, schrieb Tim Alder:
How can we bring the tool to live-system?
Well, the obvious thing would be to put it into osm's $HOME/bin and create an entry into the crontab. It would be good to keep some logfiles about the actions performed, so we can check if it's really doing what we're expecting.
Peter
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l