First bit of data from the new routing tester...
http://i1056.photobucket.com/albums/t37 ... f8afce.png
Using our trusty old test route once again, this plot shows the server response time (in milliseconds) to each routing request (grey line) with the usual yellow and red background areas denoting requests where the returned route was incomplete or non-existent. The black line is a 5-point averaging of the raw response times. The plot starts at 00:00 today and runs through to around 10:15.
What's interesting here is that throughout the period where no routes were returned, there's a corresponding drop in average response times, which suggests the server is simply rejecting the requests as they arrive rather than attempting to calculate any routes and then timing-out during the process (the request timeout parameter was set to the default 60000 for this test). Bear in mind that the response times recorded by the test client include network transit times for both the request and response packets, in addition to the processing time of the routing server itself, so the odd spike in raw response times may be down to network congestion rather than server slowdown.
Raw data captured during this test: http://chizzum.com/lmr/test1.zip
http://i1056.photobucket.com/albums/t37 ... f8afce.png
Using our trusty old test route once again, this plot shows the server response time (in milliseconds) to each routing request (grey line) with the usual yellow and red background areas denoting requests where the returned route was incomplete or non-existent. The black line is a 5-point averaging of the raw response times. The plot starts at 00:00 today and runs through to around 10:15.
What's interesting here is that throughout the period where no routes were returned, there's a corresponding drop in average response times, which suggests the server is simply rejecting the requests as they arrive rather than attempting to calculate any routes and then timing-out during the process (the request timeout parameter was set to the default 60000 for this test). Bear in mind that the response times recorded by the test client include network transit times for both the request and response packets, in addition to the processing time of the routing server itself, so the odd spike in raw response times may be down to network congestion rather than server slowdown.
Raw data captured during this test: http://chizzum.com/lmr/test1.zip
Re: Routing errors in London