summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Probe for optimal network buffer size.Robby Zambito2026-01-04
| | | | | | | | | We want to match the underlying system socket buffer. Filling this buffer minimizes the number of syscalls we do. Larger would be a waste. Also changed parser to use enums that more closely match the NATS message types.
* holy moly goes way fast!!!Robby Zambito2026-01-03
| | | | like 150 mbps now
* Kill dead code and use higher bufferRobby Zambito2026-01-03
|
* cleanup importsRobby Zambito2026-01-03
|
* Organize thingsRobby Zambito2026-01-03
| | | | Making it easier to use the server as a library
* Fix parse errors, ownership errors.Robby Zambito2026-01-03
|
* Restructuring parserRobby Zambito2026-01-03
| | | | Adding tests fore everything
* Fix double freeRobby Zambito2026-01-03
| | | | was freeing the wrong element before.
* Subject validationRobby Zambito2026-01-02
|
* Remove unnecessary explicit enumRobby Zambito2026-01-02
| | | | This can be computed (as it is now)
* Fix possible race conditionRobby Zambito2026-01-02
| | | | | | | since the queue was being set in an async task and we were then calling send asserting that the queue was set, we could have triggered a panic. didn't run into it but seemed likely to cause issues in the future. also compute the buffer size for operators at comptime.
* Move handshake from client to serverRobby Zambito2026-01-02
|
* Only check for ctrl+c every 10 msRobby Zambito2026-01-02
|
* Add branch hints for high performance messaging.Robby Zambito2026-01-02
|
* Fix connect parsingRobby Zambito2026-01-02
|
* Don't assume capacityRobby Zambito2026-01-02
|
* remove debug logRobby Zambito2026-01-02
|
* Rework pub and hpub parseRobby Zambito2026-01-02
| | | | support hpub in general, and properly support reply subjects
* (no commit message)Robby Zambito2026-01-02
|
* Support subject patternsRobby Zambito2026-01-02
| | | | clean up some tests
* broke 100 mbps!!Robby Zambito2026-01-02
| | | | | | | | | coder@08714a4174bb:~$ nats bench sub foo -s localhost:4223 14:33:02 Starting Core NATS subscriber benchmark [clients=1, msg-size=128 B, msgs=100,000, multi-subject=false, subject=foo] 14:33:02 [1] Starting Core NATS subscriber, expecting 100,000 messages Finished 0s [===============================================================================================================================] 100% NATS Core NATS subscriber stats: 934,205 msgs/sec ~ 114 MiB/sec ~ 1.07us
* Nicer loggingRobby Zambito2026-01-02
|
* Much better cleanup, still fast B)Robby Zambito2026-01-02
|
* Cleanup on errorRobby Zambito2026-01-02
|
* reorganize but crashingRobby Zambito2026-01-02
| | | | | not sure why, seems like i'm using the right allocators everywhere? need to take another pass at this later.
* formattingRobby Zambito2026-01-02
|
* Remove dead commentsRobby Zambito2026-01-01
|
* Use group to make it easier to clean up client tasks on exitRobby Zambito2026-01-01
|
* Cleanup for deinitializingRobby Zambito2026-01-01
|
* gracefully exitRobby Zambito2026-01-01
| | | | | simplify code clean up dead code
* 97 mbps !!! super fastRobby Zambito2026-01-01
| | | | | 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.
* Slower, but probably more correctRobby Zambito2026-01-01
|
* Lock subs when reading itRobby Zambito2026-01-01
| | | | should probably make a copy instead of doing io in the mutex
* Use a small stack buffer for client ioRobby Zambito2026-01-01
|
* Use master yazapRobby Zambito2026-01-01
| | | | Works against the latest master branch for zig again :)
* 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
|
generated by cgit (git 2.34.1) at 2026-02-02 15:17:00 +0000