summaryrefslogtreecommitdiff
path: root/src/server
Commit message (Collapse)AuthorAge
* Use a small stack buffer for client ioRobby Zambito2026-01-01
|
* Actually fast again???Robby Zambito2026-01-01
| | | | | | | | | | | | | | | | 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.
* reorganize some thingsRobby Zambito2026-01-01
|
* Rename ClientState to ClientRobby Zambito2026-01-01
|
* Heap allocate client buffersRobby Zambito2026-01-01
|
* Avoid queues completelyRobby Zambito2026-01-01
| | | | This is quite slow
* Reorganized thingsRobby Zambito2026-01-01
|
* things are running quite smoothly!!!compare-to-thisRobby Zambito2026-01-01
| | | | | | | | | coder@08714a4174bb:~$ nats bench sub foo -s localhost:4223 03:28:04 Starting Core NATS subscriber benchmark [clients=1, msg-size=128 B, msgs=100,000, multi-subject=false, subject=foo] 03:28:04 [1] Starting Core NATS subscriber, expecting 100,000 messages Finished 6s [====================================================================================] 100% NATS Core NATS subscriber stats: 14,691 msgs/sec ~ 1.8 MiB/sec ~ 68.06us
* Simplified a ton of things and cleaned up ownershipRobby Zambito2026-01-01
|
* some cleanup and freeingRobby Zambito2026-01-01
|
* Cleanup clientRobby Zambito2026-01-01
| | | | | | 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.
* Rename assert to expectRobby Zambito2026-01-01
| | | | Assert implies panic, expect implies error
* Fix sub parse bugRobby Zambito2025-12-31
| | | | | Was accidentally consuming one more byte than I was expecting when reaching the end of the second term. This was causing the parser to work properly in the case that a queue group was specified, but failing and consuming the next message (usually a PING) as the SID.
* Reuse portRobby Zambito2025-12-31
| | | | | This lets me dev cycle faster Shouldn't have to do this though, should be cleaning up properly
* More cleanupRobby Zambito2025-12-29
|
* Parsing cleanupRobby Zambito2025-12-29
|
* publish worksRobby Zambito2025-12-29
| | | | starting to use errors instead of unreachable for stream parsing
* (no commit message)Robby Zambito2025-12-29
|
* (no commit message)Robby Zambito2025-12-28
|
* made some progress on subscriptionsRobby Zambito2025-12-10
|
* Add branch hint for message publishRobby Zambito2025-12-09
|
* sending errors on pub sub!Robby Zambito2025-12-09
|
* The issue was the writer is not working to send pong ??Robby Zambito2025-12-09
|
* Made progress, but not perfect.Robby Zambito2025-12-08
| | | | | the message isn't crossing container boundaries, but it works in the test!
* (no commit message)Robby Zambito2025-12-06
|
* (no commit message)Robby Zambito2025-12-02
|
* (no commit message)Robby Zambito2025-12-02
|
* Switch from clap to yazapRobby Zambito2025-11-29
| | | | | This is compatible with the latest 0.16.0 nightly build. It is also a bit less magic than clap.
* (no commit message)Robby Zambito2025-11-29
|
* Can handle PUBRobby Zambito2025-11-25
|
* (no commit message)Robby Zambito2025-11-23
|
* (no commit message)Robby Zambito2025-11-21
|
* Process pubRobby Zambito2025-11-19
|
* Parse connect properlyRobby Zambito2025-11-19
|
* (no commit message)Robby Zambito2025-11-19
generated by cgit (git 2.34.1) at 2026-02-02 16:35:18 +0000