ioxide.pg
0.2.1
See the version list below for details.
dotnet add package ioxide.pg --version 0.2.1
NuGet\Install-Package ioxide.pg -Version 0.2.1
<PackageReference Include="ioxide.pg" Version="0.2.1" />
<PackageVersion Include="ioxide.pg" Version="0.2.1" />
<PackageReference Include="ioxide.pg" />
paket add ioxide.pg --version 0.2.1
#r "nuget: ioxide.pg, 0.2.1"
#:package ioxide.pg@0.2.1
#addin nuget:?package=ioxide.pg&version=0.2.1
#tool nuget:?package=ioxide.pg&version=0.2.1
A shared-nothing io_uring runtime for .NET.
One ring per reactor thread - run one per core. Each reactor owns its ring, its SO_REUSEPORT listener, its connections and its clients outright: nothing is shared, so nothing is locked. HTTP, Postgres, Redis and file I/O all submit on the owning ring and resume inline on the same thread. No thread pool on the hot path. No native dependencies - raw syscalls, nothing else.
Linux 6.1+ · .NET 10 · status
0.1.1- experimental
Documentation - architecture, guides, the full picture
First-class async/await
Shared-nothing runtimes usually ask you to give up the platform's async model. ioxide keeps it:
handlers are ordinary async Task code, and await works everywhere.
- Ring completions resume their continuations inline on the reactor thread - an awaited recv, query or file read picks up exactly where it left off, with no thread pool hop.
- A per-reactor
SynchronizationContextcatches everything that would otherwise escape: timers,HttpClient,Task.Runresults - their continuations post back to the owning reactor. - Ring operations await through reusable, allocation-free awaitables.
You always wake up on your reactor. That is what makes shared-nothing practical in .NET: connection, pool and handler state stays single-threaded without a lock in sight.
Packages
| Package | What it does |
|---|---|
ioxide |
The runtime: reactors, TCP/UDP transports, connections, the ring-native client seam. |
ioxide.pg |
Postgres driver. A pool per reactor; connect, query and stream rows on the owning ring. |
ioxide.redis |
Redis client. RESP2, pipelining, pub/sub - pooled per reactor. |
ioxide.file |
Static assets. Immutable snapshots, baked responses, positional ring reads. |
ioxide.tls |
TLS. OpenSSL handshake over the ring, then kTLS - handlers keep writing plaintext. |
ioxide.Kestrel |
ASP.NET Core transport: UseIoxide() and Kestrel runs one ring per core. |
Scope
ioxide hands you raw bytes and stays out of HTTP. Request parsing and response bytes are your
code; the runtime owns the ring, the connections and the clients. When you want a framework
on top, ioxide.Kestrel plugs the same engine under ASP.NET Core.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. net11.0 is compatible. |
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.2.3 | 4 | 7/24/2026 |
| 0.2.2 | 37 | 7/23/2026 |
| 0.2.1 | 35 | 7/23/2026 |
| 0.1.1 | 124 | 7/20/2026 |
| 0.0.17 | 379 | 6/23/2026 |
| 0.0.16 | 106 | 6/21/2026 |
| 0.0.15 | 104 | 6/21/2026 |
| 0.0.14 | 104 | 6/21/2026 |
| 0.0.13 | 105 | 6/21/2026 |
| 0.0.12 | 157 | 6/21/2026 |
| 0.0.11 | 136 | 6/20/2026 |
| 0.0.10 | 107 | 6/20/2026 |
| 0.0.9 | 112 | 6/20/2026 |
| 0.0.8 | 137 | 6/19/2026 |
| 0.0.7 | 204 | 6/17/2026 |
| 0.0.6 | 110 | 6/15/2026 |
| 0.0.5 | 124 | 6/13/2026 |
| 0.0.4 | 117 | 6/12/2026 |
| 0.0.3 | 115 | 6/12/2026 |
| 0.0.2 | 108 | 6/11/2026 |