[mkgmap-dev] mkgmap doing excessive writing and converting to disk if used with --gmapi option

Mon Sep 20 10:25:30 BST 2021

The current version is perfect. Avoids all those unnecessary writes and no
need to go crazy on symbolic links anymore for preventing them. Files that
should be overwritten - are overwritten.

On Sun, 19 Sept 2021 at 15:03, Felix Hartmann <extremecarver at gmail.com>
wrote:

> first of all I need all info.xml files - because I want different versions
> of a map possible. And yes second those files are tiny - just rename/Move
> them away before running mkgmap again. That is trivial on any system. (much
> easier than moving away all those folder and linking them back was was
> needed before this patch).
>
> On Sun, 19 Sept 2021 at 12:39, Gerd Petermann <
> gpetermann_muenchen at hotmail.com> wrote:
>
>> 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 at lists.mkgmap.org.uk> im Auftrag von
>> ael <witwall3 at disroot.org>
>> Gesendet: Mittwoch, 8. September 2021 13:31
>> An: mkgmap-dev at 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 at lists.mkgmap.org.uk
>> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>
>
> --
> Felix Hartman - Openmtbmap.org & VeloMap.org
>
>

-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210920/d03af450/attachment.html>