Slow responses from listMarketBook

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jptrader
    Junior Member
    • Nov 2009
    • 82

    #1

    Slow responses from listMarketBook

    During the last week or so I have intermittently been getting slow responses to listMarketBook. While the response times normally are < 50ms, response times are now generally higher and relatively often I get response times > 500ms. This has been tested both from London based and Dublin based servers, so it is not a server problem on my side. Anybody else experiencing this?
  • yl
    Junior Member
    • Feb 2013
    • 3

    #2
    I confirm. Response times are jumping randomly in range 70-1000 ms. Accordingly to logs these jumps started from smaller range on March 11, and rose to current values on March 13.

    Comment

    • jptrader
      Junior Member
      • Nov 2009
      • 82

      #3
      Is it possible that this is related to the timeouts from listMarketCatalogue? http://forum.bdp.betfair.com/showthread.php?t=2796

      Comment

      • Lopiner
        Junior Member
        • Feb 2009
        • 117

        #4
        Im having the same problem.
        fooledbyabet.com

        Comment

        • yl
          Junior Member
          • Feb 2013
          • 3

          #5
          Don't know. Strange things related to the problem, I've seen today are:

          From one ip (Dublin) - there is a 1/4 chance of a fixed delay of 3000 ms for any TCP connection, even without any requests. Looks like a timeout inside Betfair network, since all intermediate addresses are passed without delays.

          At the same time another ip (Eastern Europe) - shows no 3000 ms delays for same requests and connections w/o requests.

          Also, depending on location (Dublin or Eastern Europe) - response times are now enormously different. Dublin shows absolutely unstable times, varying from 70ms up to 5000 ms. For Eastern Europe response times are very stable and seems haven't changed since previous months.

          Comment

          • yl
            Junior Member
            • Feb 2013
            • 3

            #6
            Log shows that the problem was fixed yesterday.

            Comment

            Working...
            X