[mkgmap-dev] [PATCH v5]splitter memory usageFrom Felix Hartmann extremecarver at gmail.com on Thu Nov 17 15:48:58 GMT 2011
some more speed observations: country germany.pbf from Geofabrik splitter_patched with optimize-mem: 3 min 6 seconds splitter_patched without optimize-mem: 3min 2 seconds old splitter: 3 min 42 seconds I am currently running against europe.pbf, will post the results later. But it seems that the patched mkgmap is consistently a bit faster. I think optimize-mem is better of by default though (most people using mkgmap/splitter have powerful computers anyhow). I'm interested if the 1024 max areas vs the old 255 and subsequent less runs make for a bigger speedup than on small(er) extracts.
- Previous message: [mkgmap-dev] [PATCH v5]splitter memory usage: Exception in thread "main" java.lang.NoClassDefFoundError: it/unimi/dsi/fastutil/longs/Long2ShortFunction
- Next message: [mkgmap-dev] [PATCH v5]splitter memory usage
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list