Hi,
We are using the Stata wrapper of osrm to find routes for millions of
observations. I have finally deduced that one thread does not work when the
number of observations is large enough. 5 million is large enough; 1 million is
not. The return code is 3=Something else is wrong for exactly 25
Just as a point of reference, you mention that avoiding swapping and just using
RAM will be much faster. If the swap space is an SSD drive, how much does using
only RAM speed up contract? That is, what is the difference between using say a
7200 rpm SATA drive versus an SSD drive make?
_
I have been wondering the same thing. One of the benefits of OSRM is that it
can be used in a secure environment without web access. This makes it wonderful
for research purposes. However, we need a way to document what we do. This
includes being able to cite the version of the software and also
v` flag to tell you the version. Maps are not a concern of OSRM, so you will
need to deal with that outside of OSRM as well.
Best,
Johan
On Thu, Nov 30, 2017 at 9:31 PM, Sayer, Bryan
mailto:bsa...@s-3.com>> wrote:
I have been wondering the same thing. One of the benefits of OSRM is that it
Hi,
We are calculating distances between an U.S. census tract centroid and
hospitals. A tract averages about 4,000 people, but can vary in area.
Obviously, the centroid is likely to not be on a street, and thus a jump
distance has to be calculated to get to a street.
Our question is what is
/ or something to see if it
even looks reasonable.
daniel
On Tue, Jan 16, 2018 at 1:43 PM, Sayer, Bryan
mailto:bsa...@s-3.com>> wrote:
Hi,
We are calculating distances between an U.S. census tract centroid and
hospitals. A tract averages about 4,000 people, but can vary in area.
Obvi
18, 2018 12:25 PM
To: Sayer, Bryan
Cc: Mailing list to discuss Project OSRM
Subject: Re: [OSRM-talk] calculation of jump distances
Hi Bryan,
OSRM uses an R-Tree (https://en.wikipedia.org/wiki/R-tree) to do a nearest
neighbour search (https://en.wikipedia.org/wiki/Nearest_neighbor_search
We use the Stata implementation OSRMTIME from Stephan Huber at Regensburg
University which can split the data across threads (we have 2 CPUS with four
cores each, and two threads per core). So 16 threads on a 3.5 Ghz Xeon and 64
GB of RAM, and if the network traffic is low (like on holidays) I
When I had that problem it was due to lack of memory. For the United States, I
had to have 64 GB of memory prepare, though I was doing it through a Stata
interface, not directly.
From: Didier Doumerc
Sent: Thursday, August 9, 2018 11:53:39 AM
To: osrm-talk@opens
4 GB or RAM.
Is there anyway way to successfully prepare the files ? Perhaps by downloading
them ready yet ?
Thanks for your answer.
Didier
Le jeu.09/08/18 à 18:15, Sayer, Bryan a écrit :
When I had that problem it was due to lack of memory. For the United States, I
had to have 64 GB of
My experience is probably with a slightly older version of OSRM, but I found
that you have to have actual physical RAM (like 64G) to do the map extract.
Creating a big swap space isn't sufficient. Some people advise doing the
extract on an AWS cloud computer.
Bryan Sayer
_
I'm not sure what your use case is.
We use the Stata implementation from S.Huber and C. Rust to do static routing.
That is, we have a static list of starting points and ending points that we
route in batch. You do have to build your routing maps first, and this takes a
lot of memory, although
12 matches
Mail list logo
