The judges and the starter divide a machine's CPUs instead of each taking all
CI / test (push) Failing after 30m7s
CI / test (push) Failing after 30m7s
Measured on the three-VM cluster with ha1's CPUs loaded: 38 of 60 requests refused with both judges and the starter on ha1, each engine on all four cores. With the judges moved to a 4-core, 32 GB node at 2 cores each, 2 of 60 were refused, both the first after the judges started. init now reserves cores by this machine's count: one per judge replica under 8 CPUs and two from 8, and the rest, up to 8, for the starter on CPU. The starter reserves nothing when nothing is left, so it still fits. Judges bound for nodes not yet known get two each. A judge reserves 4 GB; it uses about 3.2. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
0b984a92bc
commit
63b2c6d9a4
5 files changed
+98
-12
No files matched your search
@@ -120,6 +120,9 @@ type serverInit struct {
|
||||
// whichever leads.
|
||||
standbys bool
|
||||
vip string
|
||||
// cpus is this machine's CPU count for dividing it between init's
|
||||
// models; zero asks the machine. A seam for tests.
|
||||
cpus int
|
||||
// pgSetup prepares PostgreSQL and returns the store address; a seam for
|
||||
// tests. Nil does it for real.
|
||||
pgSetup func(context.Context) (string, error)
|
||||
|
||||
Reference in new issue
Block a user