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!