Skip to content

Commit c0cce96

Browse files
committed
Document that we don't recommend multiple judgedaemons on a single machine
Closes: #2277
1 parent ebe8f21 commit c0cce96

File tree

2 files changed

+7
-2
lines changed

2 files changed

+7
-2
lines changed

doc/manual/config-advanced.rst

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -338,8 +338,11 @@ systemd, then edit the ``domjudge-judgehost.target`` unit file and add
338338
more judgedaemons there.
339339

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

344347
Multi-site contests
345348
-------------------

doc/manual/install-judgehost.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ System requirements
1919
* A TCP/IP network which connects the DOMserver and the judgehosts.
2020
The machines only need HTTP(S) access to the DOMserver.
2121

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

2325
.. _judgehost_software:
2426

0 commit comments

Comments
 (0)