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

Wed Sep 8 15:07:03 BST 2021

Well I could give it 20 GB ram disk, maybe 32 but then I need to render on
less than 12 processes 64GB ram available). But that is not enough for Asia
continent map, and I guess super tight for Europe...

Mkgmap could definitely keep those .tmp files in memory. But the important
bit is the gmap files not needeed to be written.... Also would save quite
some CPU time.

On Wed, 8 Sep 2021, 14:31 ael <witwall3 at disroot.org> wrote:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210908/82910493/attachment.html>