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

Add benchmark tool for the recording server #9120

Merged
merged 8 commits into from
Mar 22, 2023

Conversation

danxuliu
Copy link
Member

Requires #9119

Feel free to directly review/merge this one and skip #9119

@danxuliu
Copy link
Member Author

/backport to stable26

@nickvergessen
Copy link
Member

Requires #9119

Done, rebase?

@danxuliu danxuliu force-pushed the add-benchmark-tool-for-the-recording-server branch from 8232bc4 to 726eb4a Compare March 21, 2023 15:41
Rather than providing some values and then composing the final name from
them now the sink name is explicitly provided.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Rather than providing some values and then composing the final name from
them now the recorder log name is explicitly provided.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This will make easier to override the values set in the configuration
for specific runs.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The benchmark tool can be used to check the resources needed by the
recorder process with different configurations, as well as to verify the
quality of the recorded file.

Unlike a real call recording the benchmark helper does not launch a
browser and joins an actual call; instead a video file is played.
Therefore it can not be used to check the whole usage of resources
during a call recording, but only the resources used by the recorder
itself.

On the other hand, playing a video file eases performing the tests, as
it does not require an actual call to be running, and also helps to
compare the quality between different configurations, as they can all be
based on the same input.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@danxuliu danxuliu force-pushed the add-benchmark-tool-for-the-recording-server branch from 726eb4a to a1d35cd Compare March 22, 2023 14:08
Copy link
Member

@nickvergessen nickvergessen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐘

@nickvergessen nickvergessen merged commit 33cc020 into master Mar 22, 2023
@nickvergessen nickvergessen deleted the add-benchmark-tool-for-the-recording-server branch March 22, 2023 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants