987dc492a6
97 mbps !!! super fast
...
dosen't flush every message, pulls batches from the queue to send, and flushes at the end of each batch.
batches are a min of 1 message, but may be more.
2026-01-01 19:16:58 +00:00
45bd63dbe1
Actually fast again???
...
way faster than before even??
coder@08714a4174bb:~$ nats bench pub foo -s localhost:4223
05:12:23 Starting Core NATS publisher benchmark [clients=1, msg-size=128 B, msgs=100,000, multi-subject=false, multi-subject-max=100,000, sleep=0s, subject=foo]
05:12:23 [1] Starting Core NATS publisher, publishing 100,000 messages
Finished 0s [====================================================================================] 100%
NATS Core NATS publisher stats: 574,666 msgs/sec ~ 70 MiB/sec ~ 1.74us
So cool.
src/server/client.zig JJ: M src/server/main.zig JJ: JJ: Lines starting with "JJ:" (like this one) will be
removed.
2026-01-01 05:22:03 +00:00
f289ab7893
Rename ClientState to Client
2026-01-01 05:22:03 +00:00
b447883d10
Reorganized things
2026-01-01 05:22:02 +00:00
a781876038
Simplified a ton of things and cleaned up ownership
2026-01-01 05:22:02 +00:00
0f138e5984
some cleanup and freeing
2026-01-01 05:22:02 +00:00
e60a566a7c
Cleanup client
...
Break up creating and starting the client process.
I think this should simplify storing the std.Io.Queue on the stack.
Before I was storing it on the heap because it was hard to make it point to the same location if I was initializing the client on the stack.
2026-01-01 05:22:02 +00:00
fe4c1d410b
More cleanup
2025-12-29 04:56:54 +00:00
4bf5ddca15
publish works
...
starting to use errors instead of unreachable for stream parsing
2025-12-29 04:23:16 +00:00
335c4aa092
2025-12-29 00:35:06 +00:00
18f4475aaf
2025-12-28 22:22:33 +00:00
50870da1d9
made some progress on subscriptions
2025-12-10 00:11:12 -05:00
5fd580045d
Add branch hint for message publish
2025-12-09 21:16:44 -05:00
45e8c4cc08
sending errors on pub sub!
2025-12-09 18:22:41 -05:00
30cc017081
The issue was the writer is not working to send pong ??
2025-12-09 17:56:07 -05:00
1eeb55ff4d
Made progress, but not perfect.
...
the message isn't crossing container boundaries, but it works in the
test!
2025-12-08 21:09:16 -05:00
826da348a5
2025-12-06 19:45:05 -05:00
4afdf32beb
2025-12-02 22:03:17 -05:00
aceb671ddc
2025-12-02 19:53:03 -05:00
bd9ed88e5c
2025-11-29 18:30:39 -05:00
51008cd7e1
2025-11-19 08:44:40 -05:00
