Skip to content

Document that we don't recommend multiple judgedaemons on a single machine #3021

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

Merged
merged 1 commit into from
Jul 7, 2025

Conversation

eldering
Copy link
Member

@eldering eldering commented Jul 5, 2025

Closes: #2277

@eldering eldering force-pushed the doc-single-judgedaemon branch from c04d6b0 to eb33231 Compare July 5, 2025 20:00
@eldering eldering force-pushed the doc-single-judgedaemon branch 2 times, most recently from 8796f36 to 13ce10c Compare July 6, 2025 14:58
@eldering eldering enabled auto-merge July 6, 2025 16:10
@eldering eldering force-pushed the doc-single-judgedaemon branch from 13ce10c to 654a11a Compare July 7, 2025 19:24
@eldering eldering added this pull request to the merge queue Jul 7, 2025
Merged via the queue into main with commit c0cce96 Jul 7, 2025
42 checks passed
@eldering eldering deleted the doc-single-judgedaemon branch July 7, 2025 19:55
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.

Possible Linux kernel lock contention when running multiple judgedaemons per machine
3 participants