Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packets not received by server after around 130 packets in a connection #395

Closed
hari-19 opened this issue Aug 12, 2023 · 2 comments
Closed
Labels
invalid This doesn't seem right

Comments

@hari-19
Copy link

hari-19 commented Aug 12, 2023

I am running an experiment where I like to send many packets to a QUIC server. I tried opening a connection and sending packets from a client continuously (with sleep b/w packets). I noticed that the server stopped receiving the packets after around 130 packets every time. Then after a while changes, the connection state to terminated.

The sleep times I tried: 0 sec (no sleep), 1 sec, 20 sec.

Client App code: https://gist.github.com/hari-19/5e4fdeea32b80ee25724aea38e096890
Server App code: https://gist.github.com/hari-19/d495d7760b228a6bd339e119af471d54

I have attached the relevant terminal log files below. Any help on the cause of this issue would be helpful for my research.

server_20sec.log: https://gist.github.com/hari-19/e4dae248650d928760ba9c986e7ba12f
client_20sec.log: https://gist.github.com/hari-19/94a4519bc1b2a321cd2149cd55277d30

server_1sec.log: https://gist.github.com/hari-19/00688041c9dfe0b6372aac9cc65ccae6
client_1sec.log: https://gist.github.com/hari-19/825974480ebaa0883b5a5f6ce1bc0ba7

server_0sec.log: https://gist.github.com/hari-19/bb41c3b530ceb1cd06f14784e40681c0

Kudos for a great library for QUIC App development.

My setup:

The experiment was run on a Laptop with Intel i7-1260P, 16GB RAM laptop.
Client in a VMware Ubuntu 22: 8 Cores, 6 GB RAM
Server: In the Host OS (Windows 11 Home): 16 Cores, 16 GB RAM

I carried the same experiment with the server running in a laptop with Intel i5-8250U, 8GB RAM, Ubuntu 22 and Client in a laptop with Intel i7-1260P, 16GB RAM, Windows 11 Home. The observation was consistent.

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Dec 11, 2023
@jlaine jlaine removed the stale label Dec 12, 2023
@jlaine
Copy link
Contributor

jlaine commented Dec 28, 2023

You are using time.sleep(20) in your send loop, which means you are holding up the event loop for 20 seconds each time. During this time, the event loop is unable to do any work at all: you are not handling incoming packets or timers.

Try using await asyncio.sleep(20)

@jlaine jlaine closed this as completed Dec 28, 2023
@jlaine jlaine added the invalid This doesn't seem right label Dec 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants