Postgres checkpointing at 2.6GB/s. I might actually have something to talk about @PGCon
-
-
That's with postgres doing unbuffered / direct IO using io_uring. 2.6GB/s is about the drives limit. Checkpointer using about 70% CPU at that point. ~60% of that inside the kernel. A good bit due to the unnecessarily small writes.
Show this thread -
And it should be doable to optimize the PG side a good bit further. Well, time to make appending workloads not suck quite so badly (250MB/s on the same storage).pic.twitter.com/ejoWQxzOqR
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.