Hi ael,
It seems to be profligate in its use of disk cycles. Any further prove for this despite the gmapi directory? While I do agree that the whole tool chain (download complete *.osm.pbf, maybe convert to *.o5m, maybe mix with contour data, splitter, and finally compile with mkgmap) is very I/O intensive I really don't see much room for improvements in mgmap. The program keeps most of the data in memory before writing the final result, only data for the global index files which are likely to grow very large are written to tempory files.
Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von ael <witwall3@disroot.org> Gesendet: Mittwoch, 8. September 2021 13:31 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] mkgmap doing excessive writing and converting to disk if used with --gmapi option On Wed, Sep 08, 2021 at 02:10:52PM +0300, Felix Hartmann wrote:
Yes on an nvme disk you barely notice the conversion - it's really quick. BUT it is not needed if you have the files and even more - it burns your NVME SSD disk.
+1. I always use an old spinning rust disk when using mkgmap to save ssd write cycles, even without contours and such. It seems to be profligate in its use of disk cycles. I did try using RAM disk, but even with 16GB on a laptop, that was soon exhausted. ael _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev