6 ms·

Twitter:we made it

22 points by aitoehigie 18y ago

thedob 18y ago
This seems a bit analogous to the Chris Rock "Always asking for credit for things you're supposed to do" routine. Nonetheless, impressive they stayed up so well on Monday, despite the recent issues.
- sant0sk1 18y ago
  "I take care of my kids!" "What do you want? A Cookie?!?!"
  - tokipin 18y ago
    http://www.youtube.com/watch?v=et_nAV0XZt0 http://www.youtube.com/watch?v=et_nAV0XZt0
- mcxx 18y ago
  Impressive in Twitterworld. Not impressive at all anywhere else.
jeroen 18y ago
"our uptime during the event was 97.3%" ... "About 4% of requests during this time did return the page that asks folks to wait a few minutes and try again." Which means that 1 in 15 users got some sort of error. That's a lot.
- cstejerean 18y ago
  You mean 1 in 25?
  - jeroen 18y ago
    No, I don't. 97.3% uptime, minus 4% error pages == 93.3% valid responses.
    - msg 18y ago
      It's 97.3% times 96%, since it's a given that only those who got in got error pages. My calculator puts that at 93.4%. The error is more pronounced if uptime was say, 20%, and error rate was 4%. If we do it your way, it's 16%. My way, it's 19.2%.
      - jeroen 18y ago
        You are right, of course. I took a shortcut because I knew my result would only be off by a small margin, but I failed to mention that.
Mystalic 18y ago
Bare functionality, constant sightings of the "fail whale," API calls dropped to 20 and then to 10, the archives and replies function shut off, direct messages shut off... That doesn't sound like "making it" to me. What it SHOULD be doing is staying up with all functionality, like most other well-designed services. Twitter's definition of success is a far cry from mine.
- markbao 18y ago
  That's why Twhirl has been telling me 'limit exceeded' even though I'm updating every two minutes (30/hr) In fact, it's been doing that for the past month and a half...
deleted 18y ago
[deleted]
jraines 18y ago
They really should do one of two things: 1) Throw AdWords on their fail page 2) Make it a contest; for example if you happen to spot the special green Fail Whale, you win an iPod.
ericb 18y ago
I wonder if they have considered load testing twitter themselves, instead of letting their users do it. Disclosure: I'm currently writing a hosted load testing tool.
edw519 18y ago
97.3% ? They oughta send a $2.56 check to everyone they let down.
truebosko 18y ago
They may have been up, but the site was DEADLY slow. Was hard to do anything from the site (I have twhirl, but not at work)

22 points by aitoehigie 18y ago

This seems a bit analogous to the Chris Rock "Always asking for credit for things you're supposed to do" routine. Nonetheless, impressive they stayed up so well on Monday, despite the recent issues.

sant0sk1 18y ago
"I take care of my kids!" "What do you want? A Cookie?!?!"
- tokipin 18y ago
  http://www.youtube.com/watch?v=et_nAV0XZt0 http://www.youtube.com/watch?v=et_nAV0XZt0
mcxx 18y ago
Impressive in Twitterworld. Not impressive at all anywhere else.

jeroen 18y ago

"our uptime during the event was 97.3%" ... "About 4% of requests during this time did return the page that asks folks to wait a few minutes and try again." Which means that 1 in 15 users got some sort of error. That's a lot.

cstejerean 18y ago
You mean 1 in 25?
- jeroen 18y ago
  No, I don't. 97.3% uptime, minus 4% error pages == 93.3% valid responses.
  - msg 18y ago
    It's 97.3% times 96%, since it's a given that only those who got in got error pages. My calculator puts that at 93.4%. The error is more pronounced if uptime was say, 20%, and error rate was 4%. If we do it your way, it's 16%. My way, it's 19.2%.
    - jeroen 18y ago
      You are right, of course. I took a shortcut because I knew my result would only be off by a small margin, but I failed to mention that.

Mystalic 18y ago

Bare functionality, constant sightings of the "fail whale," API calls dropped to 20 and then to 10, the archives and replies function shut off, direct messages shut off... That doesn't sound like "making it" to me. What it SHOULD be doing is staying up with all functionality, like most other well-designed services. Twitter's definition of success is a far cry from mine.

markbao 18y ago
That's why Twhirl has been telling me 'limit exceeded' even though I'm updating every two minutes (30/hr) In fact, it's been doing that for the past month and a half...

deleted 18y ago

[deleted]

jraines 18y ago

They really should do one of two things: 1) Throw AdWords on their fail page 2) Make it a contest; for example if you happen to spot the special green Fail Whale, you win an iPod.

ericb 18y ago

I wonder if they have considered load testing twitter themselves, instead of letting their users do it. Disclosure: I'm currently writing a hosted load testing tool.

edw519 18y ago

97.3% ? They oughta send a $2.56 check to everyone they let down.

truebosko 18y ago

They may have been up, but the site was DEADLY slow. Was hard to do anything from the site (I have twhirl, but not at work)