[mkgmap-dev] mkgmap and threads
From WanMil wmgcnfg at web.de on Sat Nov 20 22:26:39 GMT 2010
I have observed that typically mkgmap does not use more that 2 threads. If the max-jobs parameter is set to a greater value than 2 the surplus threads are blocked in the MapMaker.loadFromFile. There is a note in the MapMaker source code: // work around non-reentrancy of GType priority stuff // by serialising the map reading Is there any chance to remove this synchronization to get a gain of more threads? What has to be done to remove the synchronization in the MapMaker class? WanMil
- Previous message: [mkgmap-dev] Flood blocker
- Next message: [mkgmap-dev] mkgmap and threads
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list