Home / Input Output / ouroboros-network
Dec 13, 1-2 AM (0)
Dec 13, 2-3 AM (0)
Dec 13, 3-4 AM (0)
Dec 13, 4-5 AM (0)
Dec 13, 5-6 AM (0)
Dec 13, 6-7 AM (0)
Dec 13, 7-8 AM (0)
Dec 13, 8-9 AM (0)
Dec 13, 9-10 AM (0)
Dec 13, 10-11 AM (0)
Dec 13, 11-12 PM (0)
Dec 13, 12-1 PM (0)
Dec 13, 1-2 PM (0)
Dec 13, 2-3 PM (0)
Dec 13, 3-4 PM (0)
Dec 13, 4-5 PM (0)
Dec 13, 5-6 PM (0)
Dec 13, 6-7 PM (0)
Dec 13, 7-8 PM (0)
Dec 13, 8-9 PM (0)
Dec 13, 9-10 PM (0)
Dec 13, 10-11 PM (0)
Dec 13, 11-12 AM (0)
Dec 14, 12-1 AM (0)
Dec 14, 1-2 AM (0)
Dec 14, 2-3 AM (0)
Dec 14, 3-4 AM (0)
Dec 14, 4-5 AM (0)
Dec 14, 5-6 AM (0)
Dec 14, 6-7 AM (0)
Dec 14, 7-8 AM (0)
Dec 14, 8-9 AM (0)
Dec 14, 9-10 AM (0)
Dec 14, 10-11 AM (0)
Dec 14, 11-12 PM (0)
Dec 14, 12-1 PM (0)
Dec 14, 1-2 PM (0)
Dec 14, 2-3 PM (0)
Dec 14, 3-4 PM (0)
Dec 14, 4-5 PM (0)
Dec 14, 5-6 PM (0)
Dec 14, 6-7 PM (0)
Dec 14, 7-8 PM (0)
Dec 14, 8-9 PM (0)
Dec 14, 9-10 PM (0)
Dec 14, 10-11 PM (0)
Dec 14, 11-12 AM (0)
Dec 15, 12-1 AM (0)
Dec 15, 1-2 AM (0)
Dec 15, 2-3 AM (0)
Dec 15, 3-4 AM (0)
Dec 15, 4-5 AM (0)
Dec 15, 5-6 AM (0)
Dec 15, 6-7 AM (0)
Dec 15, 7-8 AM (1)
Dec 15, 8-9 AM (0)
Dec 15, 9-10 AM (1)
Dec 15, 10-11 AM (0)
Dec 15, 11-12 PM (1)
Dec 15, 12-1 PM (0)
Dec 15, 1-2 PM (1)
Dec 15, 2-3 PM (0)
Dec 15, 3-4 PM (0)
Dec 15, 4-5 PM (0)
Dec 15, 5-6 PM (0)
Dec 15, 6-7 PM (0)
Dec 15, 7-8 PM (0)
Dec 15, 8-9 PM (0)
Dec 15, 9-10 PM (0)
Dec 15, 10-11 PM (0)
Dec 15, 11-12 AM (0)
Dec 16, 12-1 AM (0)
Dec 16, 1-2 AM (0)
Dec 16, 2-3 AM (0)
Dec 16, 3-4 AM (0)
Dec 16, 4-5 AM (0)
Dec 16, 5-6 AM (0)
Dec 16, 6-7 AM (0)
Dec 16, 7-8 AM (5)
Dec 16, 8-9 AM (0)
Dec 16, 9-10 AM (0)
Dec 16, 10-11 AM (0)
Dec 16, 11-12 PM (0)
Dec 16, 12-1 PM (0)
Dec 16, 1-2 PM (0)
Dec 16, 2-3 PM (0)
Dec 16, 3-4 PM (0)
Dec 16, 4-5 PM (0)
Dec 16, 5-6 PM (0)
Dec 16, 6-7 PM (0)
Dec 16, 7-8 PM (0)
Dec 16, 8-9 PM (0)
Dec 16, 9-10 PM (0)
Dec 16, 10-11 PM (0)
Dec 16, 11-12 AM (0)
Dec 17, 12-1 AM (0)
Dec 17, 1-2 AM (0)
Dec 17, 2-3 AM (0)
Dec 17, 3-4 AM (0)
Dec 17, 4-5 AM (0)
Dec 17, 5-6 AM (1)
Dec 17, 6-7 AM (0)
Dec 17, 7-8 AM (3)
Dec 17, 8-9 AM (1)
Dec 17, 9-10 AM (1)
Dec 17, 10-11 AM (0)
Dec 17, 11-12 PM (1)
Dec 17, 12-1 PM (0)
Dec 17, 1-2 PM (0)
Dec 17, 2-3 PM (0)
Dec 17, 3-4 PM (0)
Dec 17, 4-5 PM (0)
Dec 17, 5-6 PM (0)
Dec 17, 6-7 PM (0)
Dec 17, 7-8 PM (0)
Dec 17, 8-9 PM (0)
Dec 17, 9-10 PM (0)
Dec 17, 10-11 PM (0)
Dec 17, 11-12 AM (0)
Dec 18, 12-1 AM (0)
Dec 18, 1-2 AM (0)
Dec 18, 2-3 AM (0)
Dec 18, 3-4 AM (0)
Dec 18, 4-5 AM (0)
Dec 18, 5-6 AM (0)
Dec 18, 6-7 AM (2)
Dec 18, 7-8 AM (0)
Dec 18, 8-9 AM (3)
Dec 18, 9-10 AM (0)
Dec 18, 10-11 AM (0)
Dec 18, 11-12 PM (0)
Dec 18, 12-1 PM (0)
Dec 18, 1-2 PM (0)
Dec 18, 2-3 PM (0)
Dec 18, 3-4 PM (0)
Dec 18, 4-5 PM (0)
Dec 18, 5-6 PM (0)
Dec 18, 6-7 PM (0)
Dec 18, 7-8 PM (0)
Dec 18, 8-9 PM (0)
Dec 18, 9-10 PM (0)
Dec 18, 10-11 PM (0)
Dec 18, 11-12 AM (0)
Dec 19, 12-1 AM (0)
Dec 19, 1-2 AM (0)
Dec 19, 2-3 AM (0)
Dec 19, 3-4 AM (15)
Dec 19, 4-5 AM (0)
Dec 19, 5-6 AM (0)
Dec 19, 6-7 AM (1)
Dec 19, 7-8 AM (0)
Dec 19, 8-9 AM (5)
Dec 19, 9-10 AM (0)
Dec 19, 10-11 AM (0)
Dec 19, 11-12 PM (8)
Dec 19, 12-1 PM (1)
Dec 19, 1-2 PM (0)
Dec 19, 2-3 PM (0)
Dec 19, 3-4 PM (12)
Dec 19, 4-5 PM (1)
Dec 19, 5-6 PM (0)
Dec 19, 6-7 PM (0)
Dec 19, 7-8 PM (0)
Dec 19, 8-9 PM (0)
Dec 19, 9-10 PM (0)
Dec 19, 10-11 PM (0)
Dec 19, 11-12 AM (0)
Dec 20, 12-1 AM (0)
Dec 20, 1-2 AM (0)
64 commits this week Dec 13, 2025 - Dec 20, 2025
mux-leios-demo: added bursty server
The client sends an initial request, the server responds with a number
of replies, then the server terminates the protocol.

The original design had the problem that the Leios traffic was sending
data while the Praos was making another request (around 10 full
MuxSDUs), and since Praos is making more requests than Leios, it skews
the results.

TODO: the client should send how many replies to get, then the commands
to run this version would be similar to the original.
mux-leios-demo: added bursty server
The client sends an initial request, the server responds with a number
of replies, then the server terminates the protocol.

The original design had the problem that the Leios traffic was sending
data while the Praos was making another request (around 10 full
MuxSDUs), and since Praos is making more requests than Leios, it skews
the results.

TODO: the client should send how many replies to get, then the commands
to run this version would be similar to the original.
mux-leios-demo: added bursty server
The client sends an initial request, the server responds with a number
of replies, then the server terminates the protocol.

The original design had the problem that the Leios traffic was sending
data while the Praos was making another request (around 10 full
MuxSDUs), and since Praos is making more requests than Leios, it skews
the results.

TODO: the client should send how many replies to get, then the commands
to run this version would be similar to the original.