Armadillo ECDSA-113

WhoCares · #1 03-13-2026, 10:44

cjack · #2 03-13-2026, 17:49

Quote:

Originally Posted by WhoCares

Hey WhoCares, thanks for reporting the connection problems you experienced.

The "SERVER OFFLINE" errors you're seeing are caused by our network setup — we use a VPN as a reverse proxy to route traffic to the server. This intermediate hop occasionally drops connections or times out, resulting in those 502 errors. The agent handles this gracefully by retrying automatically, so no work is ever lost.

We've recently applied a server-side optimization that significantly reduced the issue (server response time went from ~2000ms down to ~2ms), but the VPN layer can still cause sporadic hiccups. We're looking into improving this path further.

Important: these brief connection blips have zero impact on computational performance. The solver keeps running on the GPU continuously — it only needs the server to submit Distinguished Points, which happens asynchronously. Even if a submission fails, it simply retries on the next cycle. Your GPU speed and contribution are not affected at all.

Thanks for your patience and for contributing to the project!

WhoCares · #3 03-13-2026, 21:27

@cjack

Not sure if this is expected behavior, but I noticed a couple of things:

1. The local console reports about 197 M/s, while the web dashboard shows around 192 M/s.
2. The speed reported by the console gradually decreases over time. It started at around 200 M/s and has slowly dropped to ~197 M/s so far.

My machine isn’t running any other CPU- or GPU-intensive workloads.

Just wondering if this difference is expected, or if I might be missing something.

cjack · #4 03-13-2026, 23:30

Quote:

Originally Posted by WhoCares

@cjack

Not sure if this is expected behavior, but I noticed a couple of things:

1. The local console reports about 197 M/s, while the web dashboard shows around 192 M/s.
2. The speed reported by the console gradually decreases over time. It started at around 200 M/s and has slowly dropped to ~197 M/s so far.

My machine isn’t running any other CPU- or GPU-intensive workloads.

Just wondering if this difference is expected, or if I might be missing something.

@WhoCares

Both are totally expected, no worries!

1. Console vs Dashboard difference (~197 vs ~192 M/s):
The local console shows a cumulative average (total iterations ÷ total time since start). The dashboard uses a server-side EMA (exponential moving average) computed from DP arrival deltas every ~10 seconds. The server measurement includes a tiny network latency overhead on each heartbeat interval, which consistently makes it read ~2-3% lower. The dashboard number is actually a more accurate picture of your current sustained throughput, while the console number is slightly inflated by the faster early-session burst.

2. Gradual speed decrease (200 → 197 M/s):
Classic GPU thermal behavior. When you first start, the GPU runs at max boost clocks while it's cool. After a few minutes it reaches thermal equilibrium and settles to sustained clocks — slightly lower. Since the console uses a cumulative average from time zero, it takes a while for the displayed number to drift down from that early burst. It'll eventually stabilize around ~195-197 and stay there. Completely normal.

Your setup is running perfectly. Thanks for contributing!

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Replacing ECDSA in Target (arma)	Mynotos	General Discussion	3	11-22-2019 00:49

The Following User Says Thank You to cjack For This Useful Post:
WhoCares (03-13-2026)

The Following 2 Users Say Thank You to cjack For This Useful Post:
Jupiter (03-15-2026), WhoCares (03-13-2026)