Improve latency tests #663
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Revalioli
commented
Dec 11, 2024
Revalioli
commented
- Run latency test for 5H
- Save only the latency of the first SV of each 4000 iteration as a temporary workaround due to current memory limitations
|
In this case, you can just create the branch to run the CI in the action tab. No need to create the PR. |
Revalioli
force-pushed
the
improve-latency-tests
branch
4 times, most recently
from
682bb75 to
43f897b
Compare
Revalioli
force-pushed
the
improve-latency-tests
branch
7 times, most recently
from
d2f0ba0 to
0d54b8f
Compare
The CI latency test uses sv_timestamp_analysis which currently only generates a report with the latency results for SV stream 0. Due to this current limitation, and the fact that sv_timestamp_analysis cannot yet efficiently process large amounts of data, record timestamps only for SV stream 0. That way, it will be possible with a future commit to run longer latency tests without having memory problems during recording and result analysis. Signed-off-by: Elinor Montmasson <elinor.montmasson@savoirfairelinux.com>
Revalioli
force-pushed
the
improve-latency-tests
branch
2 times, most recently
from
556013e to
1f215d4
Compare
Increase latency test duration from 10 seconds to 15 minutes to get more relevant results during weekly CI runs. The environment variable PCAP_LOOP is used for that. To do so, create a reusable workflow "pcap_loop" input for ci-yocto.yml which defaults to 60 (1 min) if not specified. Also set the latency duration to 1 min for other CI contexts, such as when the action is triggered by a PR. That way it won't block the CI too much during development. A ternary operator is used to conditionally set PCAP_LOOP. Signed-off-by: Elinor Montmasson <elinor.montmasson@savoirfairelinux.com>
Add the use of the optional variable bittwist_cpu to set the affinity of the bittwist process. It can be needed to obtain correct scheduling for SV sending. Signed-off-by: Elinor Montmasson <elinor.montmasson@savoirfairelinux.com>
Revalioli
force-pushed
the
improve-latency-tests
branch
2 times, most recently
from
5de0881 to
67e8581
Compare
eroussy
approved these changes
Jan 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.