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

Undocker benchmark runs. #16

Merged
merged 1 commit into from
Jan 9, 2025
Merged

Undocker benchmark runs. #16

merged 1 commit into from
Jan 9, 2025

Conversation

vext01
Copy link
Contributor

@vext01 vext01 commented Jan 9, 2025

As discussed with @ltratt, since we don't really know the performance implications of docker, and since we plan to use a dedicated machine (with fewer security concerns), run the benchmarks on bare metal.

As discussed with @ltratt, since we don't really know the performance
implications of docker, and since we plan to use a dedicated machine
(with fewer security concerns), run the benchmarks on bare metal.
@vext01
Copy link
Contributor Author

vext01 commented Jan 9, 2025

At the moment this is all set up to perform each run under the same dedicated UNIX user.

We could go one step further and have a new user created for each run, but this would be a little more involved. Do we think we should do that next? Is it worth it?

@ltratt
Copy link
Contributor

ltratt commented Jan 9, 2025

I was just thinking about that sort of thing. We should do that, but not now. We have bigger fish to fry!

@ltratt ltratt added this pull request to the merge queue Jan 9, 2025
Merged via the queue into ykjit:main with commit 3892936 Jan 9, 2025
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants