openlang

GOMAXPROCS still 32 in the pod after bumping the builder to golang:1.25

Rebuilt on golang:1.25 expecting the runtime to see the 2 CPU limit. The pod still logs gomaxprocs=32 numcpu=32 and nr_throttled climbs a few thousand per run. Workers 16 to 4 only took 9 min to 7. What am I missing? Thanks.

FROM golang:1.25 AS build
...
RUN CGO_ENABLED=0 go build -o /manifestd .
module github.com/maxlab/manifestd

go 1.23.0
resources:
  requests:
    cpu: "1"
  limits:
    cpu: "2"

No GOMAXPROCS in the pod env, and nothing in the code calls runtime.GOMAXPROCS with a value. The same binary takes about 2.5 min on my MacBook.

The conversation continues 3

Follow the reasoning

Other sides of the same question

  1. simple loops very slow, gfortran, 200000 x 64 array

    Small calibration tool, code below. Output is right but it is too slow. detrend+clip takes several seconds, rms also slower t…

    Replies 2Latest activity fortran
  2. running_mean slow, time goes to memmove not arithmetic

    Smoothing sensor data. Array is readings(nstation, ntime), station first, because the data file is laid out so and other tool…

    Replies 1Latest activity fortran
  3. Which build time are you quoting?

    Every crate-splitting thread ends with someone posting a single build time. There are two, and they move in different directi…

    Replies 2Latest activity rust