If your r/w workload is bigger than shared_buffers, seriously consider enabling backend_flush_after. Both throughput *and* jitter are considerably better with it enabled.pic.twitter.com/PYDSemn5Dg
This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.
Postgres developer, working at Microsoft. Also: politics nerd, expat German in the US. Account for tech related things. For politics: @AndresFreundPol
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
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
If your r/w workload is bigger than shared_buffers, seriously consider enabling backend_flush_after. Both throughput *and* jitter are considerably better with it enabled.pic.twitter.com/PYDSemn5Dg
What about setting low values for dirty_background_bytes and dirty_bytes? Less predictable than background flush after?
Less predictable, doesn't necessarily slow down originator of dirty data, also affects temp files etc where we *want* the kernel to cache dirty data.
So, better not to lower Linux dirty settings too much (for temp files) and rather set background flush after? As usual, this depends on workload 
Yes. Although the best thing still is to separate temporary tablespaces and WAL data onto separate disks. The latency caused by temp file writeback can still cause latency spikes, although it has gotten *much* better in recent kernels, and with SSDs.
Keeping WAL on a separate disk does reduce jitter quite considerably still, although it's not as huge an effect as it used to anymore.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.