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

[Feature Request] Performance test automation #342

Open
lsylsy2 opened this issue Mar 21, 2025 · 1 comment
Open

[Feature Request] Performance test automation #342

lsylsy2 opened this issue Mar 21, 2025 · 1 comment

Comments

@lsylsy2
Copy link

lsylsy2 commented Mar 21, 2025

Creating this issue as a feature request item for myself, planning to contribute and also use to close #327
The automation should:

  1. Run on a physical machine (Linux? Including rpi or similar boards for ARM / routers) or VM with stable performance.
  2. Run different versions of UDPspeeder, run performace test using iperf or similar tool, measure the detailed CPU usage / bandwidth / etc.
  3. Use netns / tc / etc. to simulate latency and packet drop
@lsylsy2 lsylsy2 changed the title Performance test automation [Feature Request] Performance test automation Mar 21, 2025
@lsylsy2
Copy link
Author

lsylsy2 commented Mar 21, 2025

In #326 there was discussion:

Also multiple-core is not the biggest possible improvement. I actually have investigated a avx2 enabled FEC library which can improve the performance by 10x,even if with single-core.   (Combining avx2 and multiple core, it's not hard to achieve a performance improvement of 40x)

However, avx2 optimization is not suitable for personal use; what's more important is to improve performance / efficiency on low-end devices like low-end routers, battery-powered phones, cheap virtual servers, thus make the project usable to more people, instead of empowering someone to use Gigabits of bandwidth with a high-end server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant