I am doing some performance tests over OSRM and I noticed that, although there are several threads created, only one is accepting requests/doing the hard work.
Even if I "attack" the server with thousands of concurrent petitions (and responses become slower), only one osrm-routed process is using 100% of CPU, while the rest of them are idle. Am I missing something here? Is this really a bug?
I am using JMeter to run the tests, with this configuration file[1]. I am watching processes on the server machine with the "htop" command. My server.ini file has the "Threads = N" line at the top.
Also, the behaviour of the osrm-prepare and osrm-extract is ok, they use as many threads as I configure on the .ini file.
[1]https://raw.github.com/Emergya/GoFleetLSServer/169d87a8d07c4c7bd7e89fadc15eb6b3def47a7c/src/test/resources/osrm.jmx
I am doing some performance tests over OSRM and I noticed that, although there are several threads created, only one is accepting requests/doing the hard work.
Even if I "attack" the server with thousands of concurrent petitions (and responses become slower), only one osrm-routed process is using 100% of CPU, while the rest of them are idle. Am I missing something here? Is this really a bug?
I am using JMeter to run the tests, with this configuration file[1]. I am watching processes on the server machine with the "htop" command. My server.ini file has the "Threads = N" line at the top.
Also, the behaviour of the osrm-prepare and osrm-extract is ok, they use as many threads as I configure on the .ini file.
[1]https://raw.github.com/Emergya/GoFleetLSServer/169d87a8d07c4c7bd7e89fadc15eb6b3def47a7c/src/test/resources/osrm.jmx