Page 89 of 237 FirstFirst ... 3979878889909199139189 ... LastLast
Results 881 to 890 of 2367
  1. #881
    Senior Member Fast Eddie WRC's Avatar
    Join Date
    Mar 2010
    Location
    England
    Posts
    18,782
    Like
    3,417
    Liked 9,311 Times in 4,938 Posts
    Quote Originally Posted by KiwiWRCfan View Post
    Article headed "We will perfect WRC Live TV" in this weeks Motorsport Monday contains some insight into cause of problem in accessing Monte Carlo timing on WRC.com. Underlying cause known and changes have been made to ensure the problem is not repeated.
    http://mmuk.realviewdigital.com/?iid=157793#folio=35
    Wonder how this could suddenly happen as WRC.com has been providing live times and splits for years now...

    Very poor, especially coinciding with ALL LIVE on Monte Carlo (which wasnt) and didnt show many splits.

  2. #882
    Senior Member
    Join Date
    Dec 2013
    Posts
    1,256
    Like
    5,317
    Liked 1,529 Times in 657 Posts
    Quote Originally Posted by Fast Eddie WRC View Post
    Wonder how this could suddenly happen as WRC.com has been providing live times and splits for years now...

    Very poor, especially coinciding with ALL LIVE on Monte Carlo (which wasnt) and didnt show many splits.
    I think the article explains how it happened pretty well?

  3. Likes: Rally Hokkaido (13th February 2018)
  4. #883
    Senior Member
    Join Date
    Feb 2017
    Posts
    249
    Like
    1,426
    Liked 290 Times in 113 Posts
    Anybody who's ever looked at the codebase for WRC+ can tell it's amateur hour over there. Heck, even the site design for wrc.com looks like something a high schooler made on Microsoft Frontpage 15 years ago. But they're getting better, slowly.

  5. Likes: AnttiL (13th February 2018),dnb (14th February 2018),tr4m (13th February 2018)
  6. #884
    Member
    Join Date
    Sep 2017
    Posts
    64
    Like
    286
    Liked 148 Times in 42 Posts
    Quote Originally Posted by the sniper View Post
    I think the article explains how it happened pretty well?
    Miss-integration between two services is well explained?
    At more than 3 million requests per hour, the public-facing API became overloaded
    This is something that a lot of services have trouble with after starting out or making major changes and I just can not understand it. How can they let this happen? The amount of requests can't be a surprise for them, they must have some previous data and be able to calculate a safe buffer.

    Still, non of the issues that revealed themselves during the launch was a surprise and I'm quite confident it will be stabilized quite quickly.

  7. #885
    Senior Member
    Join Date
    Dec 2013
    Posts
    1,256
    Like
    5,317
    Liked 1,529 Times in 657 Posts
    Quote Originally Posted by tr4m View Post
    Miss-integration between two services is well explained?
    "Unfortunately, WRC.com's systems and ours were not integrated correctly, and traffic from the spectating public was forwarded to our servers. At more than 3 million requests per hour, the public-facing API became overloaded. WRC.com was temporarily disabled in order to allow the rest of our clients - including the AC de Monaco - stable access to timing information. Since then, we've worked with WRC.com to ensure the problem isn't repeated"

    What more do you need to know? The names of the people at WRC.com who screwed it up?

  8. Likes: Rally Hokkaido (13th February 2018),sonnybobiche (13th February 2018),tr4m (13th February 2018)
  9. #886
    Member
    Join Date
    Sep 2017
    Posts
    64
    Like
    286
    Liked 148 Times in 42 Posts
    Quote Originally Posted by the sniper View Post
    and traffic from the spectating public was forwarded to our servers
    Well, I guess that's what happens if I start reading and commenting before finishing my first coffee. Somehow I totally missed that part, thanks for bolding it our for me.

    No need for the names of the people in WRC who screwed up, as it seems I was the one who screwed up even the most basic task of reading.

  10. Likes: sonnybobiche (13th February 2018),the sniper (13th February 2018)
  11. #887
    Senior Member AnttiL's Avatar
    Join Date
    Apr 2017
    Location
    Finland
    Posts
    9,625
    Like
    8,775
    Liked 10,522 Times in 4,616 Posts
    So if I understood correctly the WRC site was constructed in a way that every time you reloaded the splits page it made a request to the RallySafe API to load the times, whereas they could and should have had just one connection from the WRC site to RallySafe API and saved the times to WRC site for the public requests. The WRC site can handle heavy traffic, RallySafe API is not designed for that.

  12. Likes: Gregor-y (15th February 2018),Rally Hokkaido (13th February 2018),the sniper (13th February 2018)
  13. #888
    Senior Member Fast Eddie WRC's Avatar
    Join Date
    Mar 2010
    Location
    England
    Posts
    18,782
    Like
    3,417
    Liked 9,311 Times in 4,938 Posts
    Quote Originally Posted by the sniper View Post
    I think the article explains how it happened pretty well?
    How it happened, yes. But not why it happened.

  14. Likes: sonnybobiche (13th February 2018)
  15. #889
    Senior Member PLuto's Avatar
    Join Date
    Aug 2001
    Location
    Zlin
    Posts
    8,344
    Like
    490
    Liked 3,776 Times in 1,679 Posts
    Interesting interview with Wayne Christie, new president of FIA Rally commission: https://rallysportmag.com/interview-...es-commission/

  16. Likes: Mirek (15th February 2018),Rally Hokkaido (15th February 2018)
  17. #890
    Senior Member
    Join Date
    Jan 2010
    Posts
    453
    Like
    3
    Liked 24 Times in 6 Posts

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •