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

Testing real delay takes a bit longer time #8

Open
ghost opened this issue Aug 18, 2024 · 3 comments
Open

Testing real delay takes a bit longer time #8

ghost opened this issue Aug 18, 2024 · 3 comments

Comments

@ghost
Copy link

ghost commented Aug 18, 2024

real delay testing takes time longer than expected when there's about 100 configs.

@GFW-knocker
Copy link
Collaborator

you have 100+ configs in there so it take lots of time for real test to complete.
for each config, the core start from scratch in separate thread
so reduce total configs to <20 and test again

@ghost ghost closed this as completed Aug 19, 2024
@GFW-knocker
Copy link
Collaborator

@seyedness
nikaNG use regex to remove keepalive before ping
so a bit heavy on ping but worth of it
without that , background thread keeps running after ping.
that's the problem of wireguard-go and we come up with this workaround for now.

@ghost ghost changed the title bug [real delay] real delay takes long time Aug 21, 2024
@ghost ghost changed the title real delay takes long time Testing real delay takes a bit longer time Aug 21, 2024
@GFW-knocker GFW-knocker reopened this Aug 28, 2024
@GFW-knocker
Copy link
Collaborator

GFW-knocker commented Aug 28, 2024

can you please test it against 100+ number of configs?
your problem should be fixed now.
let me know if issue persist.

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