You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2024. It is now read-only.
I'm using OSRM-develop (ce784e0491) and doing this to load the shared memory:
$ osrm-datastore /absolute/path/to/data.osrm
I can see the shared memory with ipcs -m. osrm-routed is able to access this shared memory.
Then I'm using node-osrm like this, where data.ini contains same absolute paths to data:
var opts = new osrm.Options("./data.ini", true /*used shared memory*/);
var engine = new osrm.Engine(opts);
node-osrm works, but it's not using the shared memory. I can manually free the shared memory segment with ipcrm -m {shmid} and my node app still does routing, for example.
Any ideas? Is it because I'm not using the latest version of OSRM, perhaps?
The text was updated successfully, but these errors were encountered:
Nice catch @clintharris - looks like the option is parsed properly but then overwritten by GenerateServerProgramOptions. So, you need to set sharedmemory=true in your .ini for this option to stick. Overall fix is #29.
I'm using OSRM-develop (ce784e0491) and doing this to load the shared memory:
I can see the shared memory with
ipcs -m
.osrm-routed
is able to access this shared memory.Then I'm using node-osrm like this, where
data.ini
contains same absolute paths to data:node-osrm works, but it's not using the shared memory. I can manually free the shared memory segment with
ipcrm -m {shmid}
and my node app still does routing, for example.Any ideas? Is it because I'm not using the latest version of OSRM, perhaps?
The text was updated successfully, but these errors were encountered: