aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristopher Baines <mail@cbaines.net>2023-03-27 17:11:48 +0100
committerChristopher Baines <mail@cbaines.net>2023-03-27 17:11:48 +0100
commit4c11d4d42798f1ab00b4c17cf2e57522abf1437e (patch)
tree9ccbd06e56ead5063151647c597070b823c507ef
parent3c9354e1c0b0767e0121ecbd03abfe37c895e34b (diff)
downloadbuild-coordinator-4c11d4d42798f1ab00b4c17cf2e57522abf1437e.tar
build-coordinator-4c11d4d42798f1ab00b4c17cf2e57522abf1437e.tar.gz
Stop using the guix-memory-metrics-updater
The data doesn't look particularly useful, and I think the memory problem I was chasing was down to a broken hook (and poor handling of that).
-rw-r--r--guix-build-coordinator/agent-messaging/http/server.scm7
1 files changed, 1 insertions, 6 deletions
diff --git a/guix-build-coordinator/agent-messaging/http/server.scm b/guix-build-coordinator/agent-messaging/http/server.scm
index ceda10c..2928513 100644
--- a/guix-build-coordinator/agent-messaging/http/server.scm
+++ b/guix-build-coordinator/agent-messaging/http/server.scm
@@ -80,17 +80,12 @@ if there was no request body."
(get-gc-metrics-updater
(build-coordinator-metrics-registry build-coordinator)))
- (define guix-memory-metrics-updater
- (get-guix-memory-metrics-updater
- (build-coordinator-metrics-registry build-coordinator)))
-
(define datastore-metrics-updater
(base-datastore-metrics-updater build-coordinator))
(define (update-managed-metrics!)
(call-with-delay-logging datastore-metrics-updater)
- (call-with-delay-logging gc-metrics-updater)
- (call-with-delay-logging guix-memory-metrics-updater))
+ (call-with-delay-logging gc-metrics-updater))
(call-with-error-handling
(lambda ()