Hi, looks quite nice. Garbagecat reports these values: SUMMARY: ======================================== # GC Events: 1385 GC Event Types: PARALLEL_SCAVENGE, PARALLEL_OLD_COMPACTING Max Heap Space: 7228800K Max Heap Occupancy: *6697358K* Max Perm Space: 21248K Max Perm Occupancy: 8133K Throughput: 94% Max Pause: 11870 ms Total Pause: 299184 ms First Timestamp: 5507 ms Last Timestamp: 4976260 ms So, you can run splitter with --max-areas=1024 without problems. The other critical values are also ok: At the end of the split process I see "number of area dictionary entries: 7909 of 65535" The profiling data shows that the CPU is most of the time busy with the pbf read and write routines, so I doubt that your disk is the bottleneck. I am about to commit a new splitter which has a better algorithm for the pseudo areas. Ciao, Gerd Henning Scholland wrote
Oh, so I misunderstood you.
Thats the result with r221 and problem-file. http://www.aighes.de/data/mkgmap.zip
Henning
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/splitter-that-generates-problem-list-tp573401... Sent from the Mkgmap Development mailing list archive at Nabble.com.