4 ms·

Must be flooded. It hung for me for a while...

• wheels 18y ago
  It takes a while to pull the data from Twitter. It actually runs around 500 worker threads spidering Twitter, and once the count gets up high some of the requests start timing out, so yeah, the whole process takes a bit. Unfortunately, since it's a limitation in how fast we can pull data from Twitter, just throwing more hardware at the problem wouldn't help much. Performance may get better as we have a large portion of the Twitter graph cached. We expected that it'd be a little rough today when it first goes up, but on usual days it should be able to handle a more casual load. We debated if we should post it here since we were pretty sure it'd swamp the connection, but probably things will level out a bit by the end of the day. Edit: Now it's hitting the VM pretty hard since once all of those threads are actually pulling, well, data, things slow down. I may set up another VPS with more RAM here in a bit and do a DNS swaperoo. We'll see how things go.