-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
OSRM taking long time to fetch the duration matrix #6140
Comments
@hoerup Thanks for your swift response. Could you please also clarify my first question, > 400 seconds for 11 x 11 matrix is this possible? Does the Boost update fix this issue? Thank you, |
@kk2491 can you provide reproduction steps of your setup and the queries your are making? It's difficult to answer this otherwise. |
To give a background, we have OSRM server configured in GCP VM instance, and a Cloud run service which queries the OSRM server for duration matrix in less than one second time interval. I tried reproducing the issue by sending parallel duration matrix queries to OSRM server in infinite loops. I am partly successful in getting the issue reproduced. Thank you |
for reproduction I think the following is crucial:
|
@nilsnolde @mjjbell I was able to reproduce the issue. I used 3 parallel functions querying the OSRM duration matrix continuously by sending API requests. 2 of them querying for 10 x 10 matrix. And one of them was querying 222 x 222. In most cases :
However there were rare cases where it was taking > 400 seconds. Thank you |
while it's nice that you could reproduce the issue. for someone to look into it, you will need to enable them to reproduce your exact (more or less) setup and queries (commit used to build, commads & region, http queries).. |
@nilsnolde @mjjbell I have attached the nodejs script here which I used to test and reproduce the issue. Please replace the IP address of the OSRM. And also out these many iterations, I was able to find only 5 instances were the OSRM took > 400 seconds for 11 x 11 matrix.
|
@nilsnolde @mjjbell Good day. Did you guys get chance to have a look at this? |
Check the access logs for your OSRM instance. It will output a request time for each query. See if that matches with the durations your script is showing. If not, it could be an issue with the network setup. And yes, if you want further help, you need to provide details of your OSRM setup so that we can try to reproduce the behaviour:
These are all contributory factors to request time, so it's not possible to debug without them. |
@mjjbell Thanks for your details, will provide you the above details soon. |
@mjjbell Apologies for the delay in response, please find the below information.
It would be great, if you could help us to pin point the issue. Thanks in advance. Thank you |
@kk2491 Are you able to watch the CPU usage inside the container running |
@danpat That's the part we are unable to perform. |
This issue seems to be stale. It will be closed in 30 days if no further activity occurs. |
Hi All,
First of all thanks for this amazing well maintained repository.
I noticed in rare cases OSRM takes huge amount of time to fetch the duration matrix. In my case, for 11 x 11 matrix, it took more than 400 seconds.
As I was going through the issues here, noticed an issue #6039 similar to this issue.
I tried to reproduce the issue by continuously querying OSRM in loop, but it was not successful.
Could you please confirm if both are same?
Also I see that there is an MR with fix has been merged with the master 3 days ago. Do we get this latest update when we use the docker for osrm-backend?
Thank you
The text was updated successfully, but these errors were encountered: