Very long time to return isolines

Hello all

Using the default config from and texas-latest.osm.pbf, I am finding it takes a long time to calculate 90 minute isochrones (approximately 90 seconds). As I have a substantial number of isochrones to crunch through, I am curious if there are any additional optimizations.

  1. I think I am using CH, as per the graph-cache/properties file

  2. 90 minutes / 75 miles are my max use case. This distance is unsupported in the vast majority (or all?) of available 3rd party isochrone creators.

  3. Server setup: 16GB VM with 4 vcores on a recent Dell XPS15 w/ 64GB RAM (Fedora33 host, Ubuntu 18.04 guest)

  4. Launch command: java -Xmx8192M -Xms4096M -Ddw.graphhopper.datareader.file=texas-latest.osm.pbf -jar *.jar server config-example.yml

  5. Using build 5c02f7b7e from origin/master

What can I do reduce my run time from ~90 seconds per API call?

Powered by Discourse