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
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions doc/manual/config-advanced.rst
Original file line number Diff line number Diff line change
Expand Up @@ -338,8 +338,11 @@ systemd, then edit the ``domjudge-judgehost.target`` unit file and add
more judgedaemons there.

Although each judgedaemon process will be bound to one single CPU
core, shared use of other resources such as disk I/O might
still have effect on run times.
core, shared use of other resources such as disk I/O typically
still has an effect on run times.
Therefore we recommend running a single judgedaemon per physical
machine for contests where precise timing is important.


Multi-site contests
-------------------
Expand Down
2 changes: 2 additions & 0 deletions doc/manual/install-judgehost.rst
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,8 @@ System requirements
* A TCP/IP network which connects the DOMserver and the judgehosts.
The machines only need HTTP(S) access to the DOMserver.

We recommend running a single judgedaemon per physical machine.
For more details see the section :ref:`multiple-judgedaemons`.

.. _judgehost_software:

Expand Down
Loading