Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
colmmacc's profile
Colm MacCárthaigh
Colm MacCárthaigh
Colm MacCárthaigh
@colmmacc

Tweets

Colm MacCárthaigh

@colmmacc

AWS, Apache, Crypto, Irish Music, Haiku, Photography

Seattle
notesfromthesound.com
Joined April 2008

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      Rare evening technical thread: about distributed systems, exponential backoff, and the tragedy of the commons problem.

      3 replies 76 retweets 225 likes
      Show this thread
    2. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      Let's say you're running some kind of service that clients call, and it has an "availability event" ... which is, you know, PR speak for "outage". Anyway, so you have this event and you fix the problem, but that doesn't always mean that you recover right away.

      1 reply 0 retweets 11 likes
      Show this thread
    3. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      Often your clients will have started to retry their requests. Clients build up over over time, more and more of them. You can easily get into a situation where you now have way more requests than you ever ordinarily would. And this just as you are trying to recover. Uggh.

      2 replies 0 retweets 7 likes
      Show this thread
    4. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      Colm MacCárthaigh Retweeted Clare Liguori

      If you have some kind of throttling, you can apply that, but the best strategy is actually to have clients backoff. @clare_liguori has gone over this very well so read what she has to say ...https://twitter.com/clare_liguori/status/1034829330201731072 …

      Colm MacCárthaigh added,

      Clare Liguori @clare_liguori
      There are three important behaviors for fault-tolerant clients: 1) Retry 2) Timeout 3) Backoff Good client libraries have knobs for each one, so you can tune for your application's needs.
      Show this thread
      2 replies 1 retweet 22 likes
      Show this thread
    5. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      The main takeaways are to do exponential backoff and add some random jitter. Do that and the recovery will go more quickly. O.k. so what am I tweeting about?

      1 reply 1 retweet 10 likes
      Show this thread
    6. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      There's a challenge with this kind of backoff; it works well only if everyone, or at least "nearly everyone", does it. A single client could decide to be more greedy and retry more aggressively - and it's sort of in their interest.

      2 replies 0 retweets 11 likes
      Show this thread
      Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      If everyone else is well behaved, that greedy client will probably get service more quickly, they'll jump the queue basically. But the overall recovery will be slowed down a bit by the aggressive tactics. Then, if this behavior spreads, it's disaster.

      7:47 PM - 29 Jan 2019 from Seattle, WA
      • 8 Likes
      • Michele Ricciardi Sean Sill Ivan O'mahony Steffen Opel Garrett Wilkin Mario Sangiorgio tinyrobots 🅘🅐🅝 💻
      1 reply 0 retweets 8 likes
        1. New conversation
        2. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
          • Report Tweet
          • Report NetzDG Violation

          Everyone retrying aggressively makes the whole situation worse, for everyone. It's a "tragedy of the commons" - everyone acting in their own narrow self-interest actually makes everyone worse off in the end.

          2 replies 0 retweets 17 likes
          Show this thread
        3. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
          • Report Tweet
          • Report NetzDG Violation

          I often think of airport baggage belts, where people compete and huddles to get closer to the belt; we'd all be better off if we *all* just stood back a few meters. Clearer views, easier access, easier exit.

          2 replies 4 retweets 27 likes
          Show this thread
        4. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
          • Report Tweet
          • Report NetzDG Violation

          Many distributed systems really rely on this kind of community oriented cooperation. TCP, BGP, the Web, e-commerce, Cloud Services. All have examples where a kind of codified socialism, fairness and restricting individual competition, keep the systems safe and cost-effective.

          2 replies 2 retweets 17 likes
          Show this thread
        5. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
          • Report Tweet
          • Report NetzDG Violation

          It needn't be like that; industries don't have to co-operate! Stock markets are the opposite, where there's a costly (maybe wasteful) race to be the fastest and try very aggressively, producing HFT.

          1 reply 0 retweets 6 likes
          Show this thread
        6. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
          • Report Tweet
          • Report NetzDG Violation

          Blockchains are another example, where there is deliberate aggressive competition, and it's even exploited to drive a perverse consensus based on mutual mistrust.

          1 reply 0 retweets 4 likes
          Show this thread
        7. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
          • Report Tweet
          • Report NetzDG Violation

          Anyway, back to the tragedy of commons! Afaik, no-one has really found a robust solution to this beyond blocking mis-behaving clients before they spread, which also comes at expense.

          4 replies 0 retweets 4 likes
          Show this thread
        8. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
          • Report Tweet
          • Report NetzDG Violation

          IME, how it "really" works is that the folks who builds clients and services have a sort of code of honor system. Everyone recognizes that it would be a wasteful race to the bottom, and mostly self-policing works. So browsers, SDKs, etc ... all do sane, safe, decent things.

          1 reply 0 retweets 13 likes
          Show this thread
        9. Colm MacCárthaigh‏ @colmmacc 29 Jan 2019
          • Report Tweet
          • Report NetzDG Violation

          I don't really have a big technical lesson there, I just find it fascinating that huge sections of the economy can get by like that. It's very inspiring and reassuring! /EOF

          4 replies 1 retweet 35 likes
          Show this thread
        10. End of conversation

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info