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
It looks to me like they're serializing everything through the petition. I don't know what their infra looks like, but if their Postgres is running on spinning rust with synchronous commits, there's the problem. Never going to get more than 100QPS out of that.
We turn off synchronous commits (and live with the risk that a server crash at *just* the wrong moment could lose a few seconds of data); the only ways around that are to avoid serializing or to use SSDs.
I don't know how postgres does things, but even on spinning rust or super cheap microsd cards e.g. on a pi, hypothetically you could still do batching to sync multiple trx at once and those FUA commands may or may not work to reduce blocking. It's easier to do everything wrong.
I wonder how hard it would be to build a 10k qps petitions website on a rpi. (confirmation via email, maybe another 100qps of counter refreshes.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
