logo separator

[mkgmap-dev] splitter that generates problem list

From WanMil wmgcnfg at web.de on Wed Nov 7 18:06:25 GMT 2012

> 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.

 From my experience profiling is a very time consuming (=> CPU 
consuming) task. So could it also be that the disk is not the bottleneck 
while you profile the application but it is the bottleneck while you 
don't profile it? (It's just a guess...)


More information about the mkgmap-dev mailing list