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'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?
What's your sys.vm.swappiness setting?
60. I just changed it to 0, not helping.
Is the 32GB actually free, or is it cached?
Free.
memory fragmentation ?
This is linus's way of saying "you should have just disabled swap & rebooted"
First guess-- something has managed to map memory and lock it into swap? Crazy thought, but...
is flushing cached writes to disk considered a page-out?
What’s still resident in swap? This is long past the point I consider killing pids...
It really sounds like it’s refilling swap at just about the same speed that it’s draining swap. What is swappiness set to? I’d have to look up the details to interpret.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
