Skip to content

Commit dd84ea1

Browse files
Update README.md
1 parent 72a8288 commit dd84ea1

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# Standard Network Library
22
High Performance, easy to use network library supporting 16k+ concurrent clients.
3-
Provides infrastructure for high throughput message passing, P2P, Nat Traversal, Reliable Udp.
4-
</br>This repository consist one main core assembly and several serialization spesific implementation assemblies.
5-
## Core Network Liblary
3+
</br>Provides infrastructure for high throughput message passing, P2P, Nat Traversal, Reliable Udp.
4+
</br>This repository consist of main core assembly and several serialization spesific implementation assemblies.
5+
## Core Network Library
66
Network Library, which is the core of entire network library. It has all the logic associated with the network system and sub systems, starting from raw bytes to abstractions such as P2P lobbies. It provides generic templates to be used with any serialization methodology.
77

8-
### Core Models
8+
### Core Components
99
Plug&Play high performance models, working with raw bytes.
1010
- ```Tcp Server/Client model``` with dynamic buffering and queueing sub systems, bytes can come fragmented like regular sockets.
1111
- ```Tcp Byte Message Server/Client``` where bytes are sent with 4 byte lenght header. It ensure atomic message delivery without fragmentation.
@@ -25,7 +25,7 @@ Involves generic models which can work with any serialization protocol.
2525
#### Advanced Memory Management
2626
- Library implements "Shared Thread Local Memory Pool", where all byte arrays and the stream backing buffers are rented from. Memory is weak referenced. Pool allows minimum number GC cycles and automatically trims on system memory pressure.
2727
- As an example, RelayServer can relay 21 Gigabyte/s Udp traffic using 36 mb process memory with 0 GC Collects.
28-
28+
2929
#### Message Buffering
3030
- Tcp models a buffering/queueing system is implemented. This system is activated only during high load.
3131
In a nutsell, if the socket is busy sending, next messages are collected and stiched together and sent as batch when the socket becomes available again. Its like Naggle, but without sacrificing the fast sends on moderate traffic.

0 commit comments

Comments
 (0)