Armadillo ECDSA-113

[cjack]

Originally Posted by WhoCares

@cjack

There is sth. wrong with my agent.

1. The computing speed is toggling between 591 M/s and 1.4 G/s.
2. And the card name "5070 Ti" should be "4070".
3. My agent becomes #1 of leaderboard.

Maybe collide with another agent?

Hey WhoCares, thanks for reporting the speed issue!

The toggling between 591 M/s and 1.4 G/s is actually expected behavior when using --gpu-limit — it's a duty-cycle mechanism (compute burst → sleep → compute burst). The reported speed alternates between instantaneous (high) and averaged (low). Nothing wrong there, that's by design.

However, while investigating this I stumbled onto something bigger: your agent was over-reporting iteration counts by roughly 50× compared to the actual Distinguished Points it produced. All 27 other agents had a perfectly normal DP/iteration ratio (around 100%), while yours was sitting at ~2%.

This caused the dashboard to show inflated progress (135% instead of the real ~91%). We've now corrected the totals and the ETA is accurate again.

Possible cause: are you by any chance running multiple instances of the solver with the same --worker-name? That would explain it — each instance reports its own iteration count to the server, but the DP production doesn't scale proportionally if they're all fighting for the same GPU.

Quick check:

Make sure you have only one solver_fast.exe running per GPU
If you want to use multiple GPUs, use --device N to assign each instance to a different GPU, with different worker names
I've also added a server-side guard (v1.4.2) that validates the DP/iteration ratio per agent, so this kind of inflation can't happen again regardless of the cause.

Thanks for being part of the battle! Your GPU is doing great work.