# aio Published articles for aio. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Offloading I/O to Dedicated Cores: An Asymmetric io\_uring Backend for Seastar and ScyllaDB DevFeed: [Offloading I/O to Dedicated Cores: An Asymmetric io\_uring Backend for Seastar and ScyllaDB]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-07-22T18:03:10Z Content type: article Language: en Sources: [ScyllaDB]() Topics: [IO](), [io\_uring](), [Architecture & Design](), [C++](), [distributed-systems](), [Linux](), [networking](), [Latency]() Tags: [aio](), [architecture](), [c-plus-plus](), [cpu](), [design](), [engineering](), [i](), [io-uring](), [latency](), [linux](), [networking](), [performance](), [seastar](), [systems]() ### AI overview This article presents Seastar's asymmetric io_uring backend, which moves low-level I/O work from application cores to dedicated cores. It explains the shared-nothing architecture, the motivations for offloading I/O, the design trade-offs, and the comparison with Seastar's existing linux-aio backend. ### Source excerpt We moved low-level I/O execution off application cores to dedicated networking cores using Seastar's new asymmetric_io_uring backend. Explore the architecture design, trade-offs, and benchmark results. ## v20.2.2 Tentacle released DevFeed: [v20.2.2 Tentacle released]() Original publisher: [Read original article]() Author: Yuri Weinstein, Patrick Donnelly Published: 2026-06-16T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [bug](), [Vulnerabilities](), [Memory Leaks](), [Encryption](), [configuration](), [IO]() Tags: [2026](), [aio](), [blog-post](), [bug](), [ceph](), [configuration](), [en-article](), [en-blog-post](), [encryption](), [io](), [memory-leaks](), [rados](), [release](), [rgw](), [storage](), [tentacle](), [ui](), [update](), [vulnerabilities]() ### AI overview Ceph v20.2.2 Tentacle is a minor release that adds Rocky 10 package-install support and recommends updating. It fixes issues across MDS, OSD, RGW, RADOS libraries, watch/notify operations, asynchronous utilities, and the dashboard, including security vulnerabilities, memory leaks, encrypted-object lifecycle problems, and UI and configuration improvements. ### Source excerpt This is the second minor release in the Tentacle series. We recommend that all users update to this release. Release Date ¶ June 16, 2026 Notable Changes ¶ Rocky 10 package-based installs are now supported starting with v20.2.2. Please see the supported platforms for current and planned support in Ceph. MDS (Metadata Server) ¶ Segmentation fault fixed due to incorrect queueing of request retries. OSD (Object Storage Daemon) ¶ PGLog Missed List: Fixed a bug to ensure the correct version is attached to the missing list when ignoring log entries. Data Integrity Asserts: Added assertions to explicitly catch potential corruption in the OSD missing list. RGW (RADOS Gateway) ¶ Lifecycle Management: Fixed lifecycle transition issues affecting encrypted multipart objects. REST & Query Handling: RESTArgs::get_string() now properly URL-decodes incoming query parameters. RADOS / librados / neorados ¶ Linger Operations: Rewrote safety checks to eliminate use-after-free vulnerabilities and LingerOp memory leaks when an unwatch operation returns ENOTCONN. Replaced the flawed is_valid_watch() check with a safe linger_by_cookie() lookup which safely manages LingerOp references using intrusive_ptr. Ensured librados linger callbacks hold a persistent reference to LingerOp to protect against races with simultaneous linger_cancel() requests. Configured librados::IoCtxImpl::aio_unwatch() to asynchronously deliver ENOTCONN to AioCompletion instead of returning the error directly. Watch/Notify: Fixed neorados notification queue bounds enforcement so that an overflow marker is only appended on the first message exceeding capacity, rather than duplicating it on every subsequent message. Prevented double-cleanup triggers in watch/notify operations when incoming errors arrive after maybe_cleanup() runs. Fixed a bug where notify would lose original error values by ensuring it no longer attempts to decode empty responses. Enhanced io_context shutdown procedures to clear handlers and route cleanl ## PostgreSQL 18 Upgrades for AI-Era Workloads and Operations DevFeed: [PostgreSQL 18 Upgrades for AI-Era Workloads and Operations]() Original publisher: [Read original article]() Author: Sebastian Insausti Published: 2026-03-20T08:00:00Z Content type: article Language: en Sources: [SeveralNines]() Topics: [PostgreSQL](), [Software as a service](), [Transactions]() Tags: [ai](), [aio](), [async](), [latency](), [maintenance](), [performance](), [postgresql](), [postgresql-18](), [replication](), [storage](), [upgrades](), [upgrades-patches]() ### AI overview This article examines PostgreSQL 18 upgrades for transaction, analytics, SaaS, event-data, and vector-search workloads. It focuses on operational improvements including asynchronous I/O, safer upgrades that retain optimizer statistics, improved multi-column indexes, UUIDv7 support, and logical replication enhancements. ### Source excerpt Today, we're asking PostgreSQL to do more and more, like handling both transactions and analytics, powering huge SaaS platforms, managing event data, and even dipping into AI-related tasks like vector search. This intense pressure highlights some pain points: slow, unpredictable reads, rigid indexing, complex setups, and risky major upgrades. PostgreSQL 18 directly addresses these real-world [...] The post PostgreSQL 18 Upgrades for AI-Era Workloads and Operations appeared first on Severalnines.