The gzip's are mine. They're niced and ioniced, so I hope they did not cause any problems.<br><br>I need to split the planet into 190 overlapping bboxes, each of which is "manageable" on a small device like a phone, yet large enough for most routing queries :<br>
<a href="http://dev.openstreetmap.de/gosmore/test">http://dev.openstreetmap.de/gosmore/test</a><br><br>My attempts with osmosis were unsuccessful due to the amount of RAM needed. If I was just a once off occurrence, I could have used 64-bit osmosis at a time when the machine is relatively idle. But I would like to do this every week and I want to be sure it will work every week without being too disruptive to other users.<br>
<br>So I wrote a new program in C that will only need +- 2GB at the peak. Unlike osmosis it starts gzip for each output file, but is still much more efficient. More details on dev list at <a href="http://osm.org">osm.org</a><br>
<br>Once my scripts and converters are stable and bug free, the load on the system will be reduced.<br><br><div class="gmail_quote">2010/2/9 Tobias Wendorff <span dir="ltr"><<a href="mailto:tobias.wendorff@uni-dortmund.de">tobias.wendorff@uni-dortmund.de</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hallo,<br>
<br>
der Dev-Server ist gerade wieder auf allen Cores zu 100% ausgelastet.<br>
Mich wundert jedoch, wieso da teilweise bis zu 100 gzip-Prozesse<br>
gleichzeitig offen sind.<br>
<br>
Ist das ein (h)top-Fehler?<br>
<br>
Grüße<br>
Tobias<br>
_______________________________________________<br>
Devserver mailing list<br>
<a href="mailto:Devserver@lists.openstreetmap.de" target="_blank">Devserver@lists.openstreetmap.de</a><br>
<a href="http://lists.openstreetmap.de/mailman/listinfo/devserver" target="_blank">http://lists.openstreetmap.de/mailman/listinfo/devserver</a><br>
</blockquote></div><br>