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
This is what it's done over the past 24h. It got rid of most of it quickly, and then the last 100MB or so are taking forever to swap in. WTF? Over the last 50 minutes it seems it hasn't managed to swap in a single page, but it's doing I/O. What is this, an O(nᴸᴼᴸ) algorithm?pic.twitter.com/RArORjswRX
It's managed to swapoff, er, about 100KiB since that tweet (~10h)? So it's not *stuck*, but you could ask someone trained in telegraphy to transmit the swapspace contents in morse code manually and it would be faster.
Disk stats say it's *writing* 6MB/s of stuff, at 1400 IOPS or so (plausible for spinning rust on battery backed RAID card), 80% I/O usage, paging "out" 1400 pages per second. What? Why is it paging stuff *out* with >32GB of RAM free?
probably a silly question but would rebooting fix this?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
