Is there any way/place that I can download a pre-built graph of the US (just for Car and Walking)? My system doesn’t seem to have the capacity (Exit code 137) even though 32gb should be enough for a 9gb PDF. I just need to do a POC for a project and, if it works out, I’ll invest in a heftier machine.
Hey,
I don’t know of anyone that provides such a service.
Note, that you can build the graphs one after the other - once a system with car is running, you can shut down the ors, save the graphs/car-folder somewhere, change your config and build walking-graphs.
Then you might be able to load both graphs simultaneously.
Depending on your usecase, it might additionally be an option to disable some preparations, which would cut down on RAM usage.
Best regards
Thanks for that info. I have tried doing the individual profiles and also some other suggestions found here regarding the exit code 137 OOM condition - such as turning off elevation and reducing accuracy. I’ll tinker with it some more and report any success if I do find the right settings.
Hey,
I assume that you already do so, but I don’t want this to be the error here:
You have to adapt the available memory to your java process via the -Xmx and -Xms settings in your Dockerfile or docker run command.
Best regards
Yes, I have played with various values for those settings. I have 32gb and have killed every other process including AV. When it starts off, it seems to do fine for about 10 min cruising around 20gb of memory. Then it bumps up to 29gb for a few min and then exits. Interestingly, the Disk I/O percentage spends a lot of time at 100%. Also, it seems to fail right about the same time regardless of the values I set for -Xmx and -Xms (which I know are being recognized from watching the log output) or any of the prep settings. I have been able to successfully build several of the individual State .pbf’s so I know the setup in general is working. I can’t use the individual states because I have queries that cross state lines.
Well file this under “Bizarre”. After getting the same result with 10gb/24gb mem settings, I was just about to reboot and try something else when I noticed that, even though it exited, it didn’t release the memory. So I decided to give it another whirl without changing anything. Three hours and forty minutes later it completed successfully! It’s almost like it had to stretch or loosen up the system. This was just the “car” profile so I’ll try the same technique with the “walking” and see what happens. Hard to call this a fix since it could be peculiar to my system but, if anyone else is at their wits end with Exit code 137, they might give the double-clutch a shot.