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.

Sign up for GitHub

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

Jump to bottom

collect timing information #2

Open
fabiangreffrath opened this issue Nov 18, 2019 · 0 comments
Open

collect timing information #2

fabiangreffrath opened this issue Nov 18, 2019 · 0 comments

Comments

@fabiangreffrath
Copy link
Member

It will probably be interesting to call the source port in a time command in the ./testrunner script to get an impression on the run-time impact of certain features. However, I am not sure how homogenous the performance of the Travis server is and if the x gametics in y realtics information printed at the end of each run doesn't even already provide more reliable information.

What do you think?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fabiangreffrath