Upgraded Kernel. Now my experimental io_uring branch of postgres is broken :( Different backends, inheriting io_urings from the postmaster, aren't allowed to submit events anymore. Only consume. Hm.
Yea, I don't like that overhead either. It's not a bad price to pay to have to do it for journal interleaved writes - the savings are so big. But being restricted in the number of uring instances due to the memlock limits is quite painful for other IO.
-
-
The code for that doesn't yet work, but my plan is to have a few urings around that aren't *commonly* going to be shared. So processes not busy doing IO don't hog a full (optimal would be two) urings, the locking is uncontended, but we still can complete their IO if necessary.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Agree, the trade off seems right for that use case, that's worth keeping in mind. Unfortunately I think we'll just have to get used to adjusting rlimit memlock for now, until the distro side catches up and realizes we need better/higher defaults.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.