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

[TEST] Investigate latency in client functions #171

Open
levincent06 opened this issue Jan 18, 2021 · 0 comments
Open

[TEST] Investigate latency in client functions #171

levincent06 opened this issue Jan 18, 2021 · 0 comments
Labels
oldies For Vincent, Daniel, and/or Ben testing Code that demonstrates code behavior

Comments

@levincent06
Copy link
Member

In our tests, we've always had to have a sleep(1) after using client functions in order to let them take effect. Examples include sending run mode, sending gamepad input and connecting a virtual device. This is slow, given that it takes only 1ms for a signal to be processed from net handler to an already connected virtual device (as seen from tc_71_10).

We should investigate why we need to sleep for so long. This will drastically speed up our tests and potentially speed up Runtime itself.

connect_virtual_device() may take long because it involves spawning a new process for the device and connecting a socket to dev handler.

@levincent06 levincent06 added the testing Code that demonstrates code behavior label Jan 18, 2021
@benliao1 benliao1 added the oldies For Vincent, Daniel, and/or Ben label Jul 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
oldies For Vincent, Daniel, and/or Ben testing Code that demonstrates code behavior
Projects
None yet
Development

No branches or pull requests

2 participants