(iggy) branch tpc_update_readme created (now e67ea7705)

[gk...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

gkoszyk pushed a change to branch tpc_update_readme
in repository https://gitbox.apache.org/repos/asf/iggy.git


      at e67ea7705 chore(io_uring): add thread-per-core shared-nothing to readme

This branch includes the following new commits:

     new e67ea7705 chore(io_uring): add thread-per-core shared-nothing to readme

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

(iggy) 01/01: chore(io_uring): add thread-per-core shared-nothing to readme

[gk...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

gkoszyk pushed a commit to branch tpc_update_readme
in repository https://gitbox.apache.org/repos/asf/iggy.git

commit e67ea7705f241e8133eff5b786f691d089728c96
Author: numminex <g....@gmail.com>
AuthorDate: Tue Nov 11 10:41:20 2025 +0100

    chore(io_uring): add thread-per-core shared-nothing to readme
---
 README.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 0da1132de..e03bedbe2 100644
--- a/README.md
+++ b/README.md
@@ -42,12 +42,13 @@ The name is an abbreviation for the Italian Greyhound - small yet extremely fast
 
 - **Highly performant**, persistent append-only log for message streaming
 - **Very high throughput** for both writes and reads
-- **Low latency and predictable resource usage** thanks to the Rust compiled language (no GC)
+- **Low latency and predictable resource usage** thanks to the Rust compiled language (no GC) and `io_uring`.
 - **User authentication and authorization** with granular permissions and Personal Access Tokens (PAT)
 - Support for multiple streams, topics and partitions
 - Support for **multiple transport protocols** (QUIC, TCP, HTTP)
 - Fully operational RESTful API which can be optionally enabled
 - Available client SDK in multiple languages
+- **Thread per core shared nothing design** together with `io_uring` guarantee the best possible performance on modern `Linux` systems.
 - **Works directly with binary data**, avoiding enforced schema and serialization/deserialization overhead
 - Custom **zero-copy (de)serialization**, which greatly improves the performance and reduces memory usage.
 - Configurable server features (e.g. caching, segment size, data flush interval, transport protocols etc.)
@@ -97,8 +98,6 @@ We do also publish edge/dev/nightly releases (e.g. `0.5.0-edge.1` or `apache/igg
 ---
 
 ## Roadmap
-
-- **Shared-nothing** design and **io_uring** support (PoC on experimental branch, WiP on the main branch)
 - **Clustering** & data replication based on **[VSR](http://pmg.csail.mit.edu/papers/vr-revisited.pdf)** (on sandbox project using Raft, will be implemented after shared-nothing design is completed)
 
 ---
@@ -453,7 +452,7 @@ For example, to run the benchmark for the already started server, provide the ad
 
 Depending on the hardware, transport protocol (`quic`, `tcp` or `http`) and payload size (`messages-per-batch * message-size`) you might expect **over 5000 MB/s (e.g. 5M of 1 KB msg/sec) throughput for writes and reads**.
 
-**Iggy is already capable of processing millions of messages per second at the microseconds range for p99+ latency**, and with the upcoming optimizations related to the io_uring support along with the shared-nothing design, it will only get better.
+**Iggy is already capable of processing millions of messages per second at the microseconds range for p99+ latency**
 
 Please refer to the mentioned [benchmarking platform](https://benchmarks.iggy.apache.org) where you can browse the results achieved on the different hardware configurations, using the different Iggy server versions.