Hey Tariq, This heavily depends on the settings you use and the kind of requests. For the car profile Germany should fit into 16GB of RAM, but I would calculate some buffer depending on if you need the option to exclude motorways and ferries. I'll assume you don't need traffic support? Then using or Contraction Hierarchy toolchain might be your best option.
For the CPU requirement to get close to 200 req/sec it entirely depends on the kind of request (how many input coordinates). For a 100x100 matrix you can expect something like ~100ms on Germany, that would put you at 10 req per core per second. A 16 core system should probably get you in the right order of magnitude. Best, Patrick On Tue, Mar 27, 2018 at 12:49 PM, Baig, Tariq <tariq.b...@ds.mpg.de> wrote: > Dear all, > > we are currently working on a research project that uses osrm as a routing > backend. > Since we heavily rely on OSRM we would like to migrate it to a more > appropriate harware setup. > > What would be the recommended specs for a server that provides routing for > the whole of germany, > and can service order of 100 - 200 table requests per second? > > Greetings and thanks in advance, > > tariq > > ---------------------------------------------------------------------------------- > > Tariq Baig-Meininghaus > > Researcher > > Max Planck Institute for Dynamics and Self-Organization > Department DCF/EcoBus > > Am Faßberg 17 > > 37077 GÖTTINGEN > GERMANY > > > Mail: tariq.b...@ds.mpg.de > > Web: www.ds.mpg.de, ecobus.fokos.info > > _______________________________________________ > 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
