[mkgmap-dev] splitter r247
From Lambertus osm at na1400.info on Fri Nov 30 18:57:47 GMT 2012
Maybe because I forgot to change the -max-areas setting the split took a lot longer then expected. It even did not finish yet. CPU usage is around 1 to 4% now, this doesn't look good. I've attached the log. The commandline I used was: java -agentlib:hprof=cpu=samples,depth=20 -XX:-HeapDumpOnOutOfMemoryError -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -Xmx6000m -jar splitter.jar --output=xml --keep-complete --overlap=0 --no-trim --mapid=1 --max-nodes=1500000 --max-areas=512 --write-kml=initial.kml --geonames-file=cities15000.zip planet-latest.osm.pbf I'll start the split again using --max-areas=2048 On 30-11-12 01:53, GerdP wrote: > > The results were ok, only runtime and memory usage was too high in > your case. r250 corrects this. > > If you want to provide new logs, please run this version with java > -agentlib:hprof=cpu=samples,depth=20 -XX:-HeapDumpOnOutOfMemoryError > -XX:+PrintGCTimeStamps +PrintGCDetails -Xmx6000m -jar splitter.jar > .... --max-areas=2048 > > This should result in max. 2 hours runtime. > > If you want to compare with the previous results, try also with > --max-areas=255 > > Please send me the splitter log and the java.hprof . > > Gerd > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20121130/695f04a8/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: split.log.zip Type: application/zip Size: 678906 bytes Desc: not available Url : http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20121130/695f04a8/attachment.zip
- Previous message: [mkgmap-dev] splitter r247
- Next message: [mkgmap-dev] splitter r247
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list