Giters

graphhopper / map-matching

The map matching functionality is now located in the main repository https://github.com/graphhopper/graphhopper#map-matching

Home Page:https://www.graphhopper.com/open-source/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Strange behavior in response time

holydrinker opened this issue · comments

commented

Hi guys,
I'm playing with GraphHopper API, and I noticed a strange behavior.

This is what I do:

  • I choose a series of 24 gps point
  • I perform map matching using on the website (here is my request with points already inserted)
  • I perform map matching in my scala application using the java dependencies graphhopper-reader-osm v0.9.0 and graphhopper-map-matching-core v0.10.0

My question is about the response time. I used the chrome console to check the response time from the website, and I timed just the "doWork" function in my code.

  • Response time from website: about 80ms
  • Response time from java application: about 800ms

How can this be possible? Is a normal behavior or am I missing something?
Thank you very much.

commented

Questions should go to the forum.

How can this be possible?

You should update your dependencies. Read the map matching part here https://www.graphhopper.com/blog/2018/09/24/september-news-from-graphhopper/