Routing errors in London

Image

Moderators: Unholy, Timbones

Re: Routing errors in London

Postby Twister-UK » Mon Jan 06, 2014 8:06 am

A shade over 8 hours into the start of a new logging session, and so far everything is proceeding as usual. Unfortunately. One of these days I'll check the results and see the routing server hasn't fallen over at the start of the morning rush hour, but that day isn't today... Oh well, it'll all get fixed "soon", right.
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Fri Jan 03, 2014 11:29 pm

As requested by David, I've uploaded some further test results obtained in early December... Data was logged between midday on the 7th until early morning on the 10th.

On the 7th and 8th routing results were pretty much OK, as expected for a weekend. On the 9th the usual pattern emerged, with routing failing completely during the morning and evening rush hours. Logging was stopped on the 10th before any rush-hour effects could creep into the data for that day.

Raw data for this test: http://chizzum.com/lmr/test5.zip


Notes on the CSV file layout...

The first 4 columns contain data common to all routes returned in the request:
Columns 1&2 - Date/time of request
Column 3 - Elapsed time (ms) between submitting request and receiving response
Column 4 - 0 if any routes were returned, 1 if no routes were returned

Each returned route then adds 5 columns as follows:
Column 5 - 0 if route reached the exact expected endpoint, 1 if it did not (no matter how close it got)
Columns 6&7 - actual endpoint coordinates
Column 8 - route distance
Column 9 - route time
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Sat Dec 07, 2013 5:33 pm

Don't know if it was an error in the route tester or with the routing server, but for around an hour or so from half 10 this morning I wasn't getting any responses logged from the server. I killed the tester and then restarted it just before 1pm, and since then it's been consistently getting results where both routes aren't reaching the required endpoint which isn't something I've seen occur for such an extended period of time. So it looks as if *something* is going on with the server, and fingers crossed it's intentional rather than just another snafu.
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Wed Dec 04, 2013 7:56 pm

Based on the results logged so far, it appears things are still being rolled around within the server room...
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Tue Dec 03, 2013 5:07 pm

Just fired up the automated test code used to generate the previous sets of results, and using the same routing request as before (see Shira's earlier post for details) I'm not getting any routes returned at the moment (6 requests made so far). I'll leave the code running for a few hours to see when routes start to appear...
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Thu Oct 24, 2013 8:58 pm

Using the same routing parameters as before, another 2-day test was run earlier this week. Comparison with the results from the previous test suggests a whole load of absolutely nothing has been done to improve routing server behaviour...

Day 1 (21st October):

Between 06:04 and 06:39 the returned routes flipped around, with the shortest route returned as the first result rather than the second.

The shortest route failed to reach the expected endpoint between 06:04-06:51.

Between 06:40-06:51 only a single route was returned.

Routing failed completely between 06:52-07:49, and again between 17:17-17:23 and 17:25-17:33 (the server managed to return both routes at 17:24)

The quickest route never reached the expected endpoint, although in most of the results it was very close (51.4595492,-0.067670527 vs the expected 51.45954977,-0.06766258).


Day 2 (22nd October):

IIntermittently between 05:53 and 06:44 the returned routes flipped around, with the shortest route returned as the first result rather than the second.

The shortest route failed to reach the expected endpoint between 06:09-06:10, 06:12-06:18, 06:20-06:21, 06:24-06:37, and 06:41-06:44.

Routing failed completely between 07:33-08:50, and again between 16:36-18:37.

Between 01:57-02:02, no responses were received from the server.

The quickest route consistently reached the expected endpoint between 03:08-06:23 (with intermittent complete routes returned between 02:29-03:05 and 06:34-06:36), at 11:54, 12:59-13:00 and 13:06, and then from 19:24 until 23:59 where logging ended.


Raw data for this test: http://chizzum.com/lmr/test4.zip


Notes on the CSV file layout...

The first 4 columns contain data common to all routes returned in the request:
Columns 1&2 - Date/time of request
Column 3 - Elapsed time (ms) between submitting request and receiving response
Column 4 - 0 if any routes were returned, 1 if no routes were returned

Each returned route then adds 5 columns as follows:
Column 5 - 0 if route reached the exact expected endpoint, 1 if it did not (no matter how close it got)
Columns 6&7 - actual endpoint coordinates
Column 8 - route distance
Column 9 - route time
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Fri Oct 18, 2013 10:16 pm

Slight change in the request arguments, plus enforced use of a https request which meant having to set up SSL support in Indy... With that now working OK, a quick check of the revised code shows that it's able once again to retrieve the test route used previously - I'll leave it running overnight to make sure it's stable on an extended run, and then fingers crossed we should be good to go next week.
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Fri Oct 18, 2013 4:50 pm

I'll have to check and see if the route tester still works after the Livemap changes, but yeah, should be able to do another run next week.
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Tue Sep 10, 2013 9:27 pm

With almost 2 full days of data captured, logging has now stopped and a summary of the results is as follows:

Day 1 (9th September):

At 01:44 and 01:46 the returned routes flipped around, with the shortest route returned as the first result rather than the second.

The shortest route failed to reach the expected endpoint between 06:17-06:49.

Between 06:50-07:00 only a single route was returned.

Routing failed completely between 07:01-07:24, and again between 17:04-17:31


The quickest route never reached the expected endpoint, although in most of the results it was very close (51.4595492,-0.067670527 vs the expected 51.45954977,-0.06766258).


Day 2 (10th September):

The shortest route failed to reach the expected endpoint between 06:03-06:42.

Routing failed completely between 07:47-09:05, and again between 16:33-18:35.

The quickest route reached the expected endpoint between 02:57-06:19 and from 19:24 to the end of logging at 22:08.


Raw data for this test: http://chizzum.com/lmr/test3.zip


Notes on the CSV file layout...

The first 4 columns contain data common to all routes returned in the request:
Columns 1&2 - Date/time of request
Column 3 - Elapsed time (ms) between submitting request and receiving response
Column 4 - 0 if any routes were returned, 1 if no routes were returned

Each returned route then adds 5 columns as follows:
Column 5 - 0 if route reached the exact expected endpoint, 1 if it did not (no matter how close it got)
Columns 6&7 - actual endpoint coordinates
Column 8 - route distance
Column 9 - route time
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

Re: Routing errors in London

Postby Twister-UK » Mon Sep 09, 2013 11:57 am

Logging was started at around 10pm last night. Monitoring the live output whilst having breakfast this morning (around 7am) I noticed a few requests that were returning only a single route or none at all, so in that respect the routing server appears to be behaving as per the previous tests, and this test should be able to supply the data that Shira and her team requires.

Slightly worrying though is that for all of the requests I observed (even during setting up the test last night) where both routes were returned, the quickest route never quite made it to the requested endpoint. Whilst this is expected behaviour in busy periods, 10pm on a Sunday evening isn't what previous testing would indicate to be a busy period - when I get a chance to examine the full logs in detail tonight it'll be interesting to see if any requests returned the correct endpoints for both routes...
Chris (not to be confused with Chris or Chris...)
L4 AM SE England & Shetland Islands / WME Beta Tester / Script Writer
WME/Livemap enhancement scripts @ GreasyFork and Chrome Web Store
Twister-UK
Beta tester
Beta tester
 
Posts: 5810
Joined: Sat Jan 07, 2012 12:00 am
Location: NW London
Has thanked: 440 times
Been thanked: 2598 times

PreviousNext

Return to United Kingdom

Who is online

Users browsing this forum: Trafiz