Query performance is also limited by disk performance as part of the
RTree that is used for the nearest neighbor lookup is on disk. You
might want to check your IO stats as well.

On Thu, Nov 12, 2015 at 3:55 PM, Daniel Patterson <dan...@mapbox.com> wrote:
> Hi Peter,
>
>   How are you performing the tests?  From the same machine, or from another 
> machine over the network?
>
>   OSRM responses are usually around 5-20ms.  If you're doing some analysis of 
> the results, on the same machine,
>   it's possible that your tests themselves are CPU limited.  Can you give 
> more info on your testing setup?
>
> daniel
>
>> On Nov 12, 2015, at 5:59 AM, Peter Becker <floyd....@gmail.com> wrote:
>>
>> I'm a little bit confused.
>>
>> i have load the map in memory with osrm-datastore und run one instance with
>>
>> "osrm-route --shared-memory=yes -t 1 -p 5000"
>>
>> with only one thread, one cpu-core raise up tzo 90% and i get ~500
>> routes per second
>>
>> if i set thread count to more then 2 or more
>>
>> "osrm-route --shared-memory=yes -t 2 -p 5000"
>>
>> 3 cpu-cores are raise up to 30-50% usage and i only get ~333 routes per 
>> second.
>>
>> so i also try run 2 instances with one core:
>>
>> "osrm-route --shared-memory=yes -t 1 -p 5000"
>> "osrm-route --shared-memory=yes -t 1 -p 5001"
>>
>> and use ngnix as load-balancer .. it dosn't make a difference to one
>> instance with 2 or more threads
>>
>> what is wrong? with "-t 2" or 2 instances i expect that 2 cpu-cores
>> are at 100% and i get more routes per second as with "-t 1".
>>
>> _______________________________________________
>> OSRM-talk mailing list
>> OSRM-talk@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/osrm-talk
>
>
> _______________________________________________
> OSRM-talk mailing list
> OSRM-talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osrm-talk

_______________________________________________
OSRM-talk mailing list
OSRM-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osrm-talk

Reply via email to