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
I'd find it a lot easier to sympathize with the latest target of a Linus outburst if I hadn't recently realized that XFS *blocks on IO to evict clean cache pages/inodes*, murdering the latency of *any* memory allocation. Clearly Chinner does *not* know how caches (should) work.pic.twitter.com/le83pX6qKK
Seriously if you use XFS then random writes into a *pipe* will block on IO after all your RAM is used by the page cache (clean cache! so, like every normal system) when the pipe tries to allocate some pages for its buffer. It's utterly broken.
Or maybe that's why he thinks the page cache is slow, because his filesystem makes it block on IO when no other filesystem does? :-)
I still remember inheriting from a former colleague the trio from hell: MySQL+XFS+mdraid. After trying to tweak the crap out of that mess to get acceptable TPS, I gave up and moved the db on a machine with ext4 and battery-backed hardware RAID array.
excuse me what
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
