CFS Edge Pool — Node Test Results

7 home nodes serving the AWS box over SSH reverse tunnels. 6/7 online  ·  polled 2026-07-12 17:43:13 UTC
NodeAssigned jobResult (live from node)Load avg
p1
192.168.1.89 · :9101 · 12c/31GB
1 + 1 = ? 1 + 1 = 2 [ran on p1] 0.00
m102
192.168.1.102 · :9102 · 4c/31GB
print "hello, world" hello, world [ran on m] 0.00
zenserver
192.168.1.242 · :9103 · 12c/15GB
print "hello, Zen Server, are you OK?" hello, Zen Server, are you OK? [ran on zenserver] 0.00
a1
192.168.1.24 · :9104 · 2c/7GB
"Hello, a1, are you a1?" Hello, a1, are you a1? [ran on a1] 0.05
l2
192.168.1.250 · :9105 · 4c/23GB
"Hello, l2, are you l2?" Hello, l2, are you l2? [ran on l2] 0.00
l4
192.168.1.212 · :9106 · 2c/3.7GB
"Hello, l4, are you l4?" offline — Failed to connect to 127.0.0.1 port 9106 after 0 ms: Couldn't connect to server
m1
192.168.1.244 · :9107 · 12c/15GB
"Hello, m1, are you m1?" Hello, m1, are you m1? [ran on m1] 0.11
Each node ran its assigned workload locally and wrote the output to ~/cfs-edge/result.txt; the worker reports it live and the [ran on <hostname>] tag proves which machine produced it. Refresh to re-poll. Load balancer for real traffic lives at /edge/<path> (round-robins across the pool).