[GraphHopper] Running out of heap space when starting webapp with large .osm.pbf

[Nate Atkinson]

Hi Emux,

That's correct-- I'm working with the webapp.

I've changed the config file to "graph.dataaccess=MMAP_STORE_SYNC"
rather than RAM store. It doesn't seem to affect when java crashes.

If I watch memory usage in 'top', it looks like java is consistently
crashing at around 2.1 GB of memory use, despite using the command line
flag "-Xmx7g" which I'm told should allow up to 7 GB heap size.

I'm going to try using Sun's JRE rather than the FOSS one that ships
with Debian. I just need to get Debian's make-jpkg tool working with the
JRE downloaded from Sun...

Best regards,

Nate Atkinson

On 10/10/2014 08:05 AM, Emux wrote:
> (Please, I'm just using GraphHopper like everybody else)
> 
> The question refers to webapp (not Android), so I think it involves Java
> parameters for memory.
> I also have see memory issues with Java client and for this I prefer to
> use GraphHopper in memory mapped mode.
> 
> -- 
> Emux
> Cruiser <http://wiki.openstreetmap.org/wiki/Cruiser> - Atlas
> <http://wiki.openstreetmap.org/wiki/Atlas_%28navigation_application%29>
> 
> 
> _______________________________________________
> GraphHopper mailing list
> GraphHopper at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/graphhopper
>