[mkgmap-dev] splitter r250 - mkgmap memory consumption

Tue Dec 4 15:53:13 GMT 2012

possible.

Please try to make sure to keep the splitter from creating tiles with 
very few nodes. The current tile algo is less likely to create too large 
(crashing on compilation) or too small (crashing the gps device). I did 
notice that it usually created more tiles in comparison with trunk 
though at same max-nodes setting.
On 04.12.2012 16:46, GerdP wrote:
> Felix Hartmann-2 wrote
>> Why does mkgmap (not mkgmap splitter!) need much more (~20% e.g. on
>> France osm.pbf geofabrik extract) RAM when working with tiles splitted
>> with 250 vs trunk splitter version (using keep-complete and overlap=0)?
>> I didn't try out intermediate versions though.
>> With 8GB Ram on the compiling machine, I needed to back down max-jobs=4
>> to max-jobs=2 in order to compile France without running out of memory
>> (java xmx 6800M).
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at .org
>> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> Probably because it uses it different algorithm to create the tiles.
> I assume that you also run into a special case, e.g. with coastlines
> described here:
> http://gis.19327.n5.nabble.com/splitter-r246-tp5737445p5737749.html
>
> Anyhow, the algorithm in r250 is creating too many tiles, so
> I am working on a different one.
>
> Gerd
>
>
>
>
>
> --
> View this message in context: http://gis.19327.n5.nabble.com/splitter-r250-and-open-questions-reg-bounding-polygon-tp5738360p5739043.html
> Sent from the Mkgmap Development mailing list archive at Nabble.com.
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- 
keep on biking and discovering new trails

Felix
openmtbmap.org & www.velomap.org