[mkgmap-dev] [PATCH v5]splitter memory usageFrom Felix Hartmann extremecarver at gmail.com on Thu Nov 17 22:17:02 GMT 2011
On 17.11.2011 22:38, GerdP wrote: > Hello Felix, > > okay, thanks again for these numbers. Just one remark regarding speed: > My profiling programs says that ~ 3% of the time is now spent in the > routines that store the data (Node2AreaMap and below). So, I can't get this > much better. Most of the time is spent reading and writing pbf and > converting the data between pbf format and internal format. So the biggest speedup would then be a faster HDD or even better a SSD. Well maybe I try it out locally on my PC with SDD tomorrow (though my CPU is much slower, but nice to see where the bottleneck is) > > The speed difference between max-nodes 900000 and 1100000 probably comes > from the different amount of data written to the pbf files. The smaller the > areas, the more data is written to more than one output file, and that slows > down processing. Oh yes, that is well possible. Even more as I use --overlap=4000 (instead of default 2000).
- Previous message: [mkgmap-dev] [PATCH v5]splitter memory usage
- Next message: [mkgmap-dev] routing on new devices
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list