[talk-au] Australian maps for Garmin devices

[stevea]

For many years,

java -Dsun.java2d.opengl=true -Xmx2048m -jar /Applications/josm-tested.jar

has been the method by which I "launch" JOSM (via my Terminal window under macOS 11).  Well, macOS 11, 10.15, 10.14 and much earlier; around macOS 10.13 transitioning to 10.14, I went from -Xmx1024m to -Xmx2048m (1 GB of RAM vs. 2 GB of RAM) for a JOSM session in my .cshrc alias.

In short, it is entirely believable that "providing more memory for java due to errors" (using 2 GB vs. 1. GB) of memory is completely comprehensible and sensible to me, as I myself have experienced (in the last several years) this exact sort of (RAM footprint) growth in my "edit-ability" of JOSM sessions as OSM (data) have grown.  2 GB remains comfortable, but I imagine it may be time to specify -Xmx4096m as a next step in subsequent months or years.  It's something I keep my eye on regarding performance, debug output and so on.

Here, I simply offer ajt1047 at gmail.com and ibennett at tpg.com.au my real-life experience of what I've done in the last several years with JOSM and java-launch RAM footprints.  Perhaps it helps validate their experiences.  OSM grows, OSM data grows, OSM data DENSITY grows, OSM RAM footprints to launch a (java) editor grow, it sort of depends on whether 1 GB, 2 GB 4 GB of RAM is reasonable.  For now, 2 GB seems reasonable for the medium-task edit complexities I ask JOSM to perform, and this command-line specification remains currently satisfactory.

SteveA

> On May 1, 2021, at 12:13 AM, Ian Bennett <ibennett at tpg.com.au> wrote:
> Andy,
> 	Thanks for this; saved me translating my terrible notes :-)
> For everyone else,
> 	This is near enough to the steps I follow. I have written a VERY basic script to do all this as I'm basically lazy....
> 	I do an extra step to include shonky maps (for contours) which also generates the gmpasupp.img that my '60 understands. Later models can digest multiple .img files.
> 	From memory (pun intended), I had to provide more memory for java due to errors (I use 2000M instead of Andy's 1200M).
> 	I highly recommend reading the man page for mkgmap.jar as the options are many.
> Ian