8 plus Days for ECM-CN WU?

[Petrctale]

BOINC estimates 79 days to complete ECM-CN WU.
it's been running 2 days 2 hours and is 22.745% done, I estimate it will take 8 to 9 days total time to complete. Is an acceptable length of time?

Thanks Boinc'er

Application
ecm 705.02
Name
ecm_cn_1738840531_2_2378L_4567_P1
State
Running
Received
2/8/2025 8:02:56 AM
Report deadline
2/18/2025 8:02:56 AM
Estimated computation size
2,469,996 GFLOPs
CPU time
1d 21:06:35
CPU time since checkpoint
1d 21:06:35
Elapsed time
2d 02:19:44
Estimated time remaining
72d 05:25:09
Fraction done
22.759%
Virtual memory size
1.73 MB
Working set size
1.66 MB
Directory
slots/1
Process ID
2988
Progress rate
0.360% per hour
Executable
ecmwrapper_705.02_windows_x86_64.exe


Computer information
IP add
Total Credit 186,114.06
Recent average credit 3,503.41
CPU type GenuineIntel
12th Gen Intel(R) Core(TM) i7-1260P [Family 6 Model 154 Stepping 3]
Number of CPUs 16
Operating System Microsoft Windows 11
Core x64 Edition, (10.00.26100.00)
Memory 65247.05 MB
Cache 2048 KB
Swap space 69343.05 MB
Total disk space 475.74 GB
Free Disk Space 352.59 GB
Measured floating point speed 2558.06 million ops/sec
Measured integer speed 17241.03 million ops/sec
Average upload rate 141796.05 KB/sec
Average download rate 4320.35 KB/sec
Average turnaround time 0.8 days
Maximum daily WU quota per CPU 500/day
Results 161
Number of times client has contacted server 692
Last time contacted server 10 Feb 2025 12:57:10 UTC
% of time BOINC client is running 99.6398 %
While BOINC running, % of time work is allowed 99.9579 %
Result duration correction factor 9.022771

[yoyo]

Lot of results have already returned.
There I see runtimes mostly between 26 and 55 hours.
Only few needed 80 hours.

yoyo

[Petrctale]

Windows auto-update rebooted my computer and the 10 ecm wu appear to have started over. I thought there were checkpoints? is it still worth letting this finish? Elapest time is 3 min CpU time is 2 d 22 h


Application
ecm 705.02
Name
ecm_cn_1738840531_2_2378L_4567_P1
State
Running
Received
2/8/2025 8:02:56 AM
Report deadline
2/18/2025 8:02:56 AM
Estimated computation size
2,469,996 GFLOPs
CPU time
2d 22:03:14
CPU time since checkpoint
00:02:40
Elapsed time
00:03:19
Estimated time remaining
73d 06:26:09
Fraction done
0.028%
Virtual memory size
1.25 MB
Working set size
7.05 MB
Directory
slots/1
Process ID
19664
Progress rate
0.360% per hour
Executable
ecmwrapper_705.02_windows_x86_64.exe

WOW finally did finish 77 hours

[VictordeHollander]

@yoyo

I would classify not resuming from checkpoint as a bug in the ecm wrapper, because the GMP-ECM application itself does create checkpoints.
<app_file>ecmwrapper_705.02_windows_x86_64.exe</app_file>
<app_file>ecm-svn3013-x64-core2.exe</app_file>


For instance this WU:
2_2354L
B1: 25000M





Content of the job.xml:
<job_desc>
<task>
<application>ecm</application>
<stdout_filename>out</stdout_filename>
<checkpoint_filename>checkpnt</checkpoint_filename>
</task>
</job_desc>


The checkpnt file containts:
METHOD=ECM;
B1=21161142943; N=5618608313315511751899218794886834868853764586441956992016177988247324759675952849494549767265823976177332875410047577820063715197493464679147956907965188822237624982126321328944165461621527766653500567866992296006813808578716872228138660965619485989018587387996039407833;
X=0x7216b9538fcc86d6eb368953924c0472aaa365fce628ce5467aaec81cac7c71008d1e34a2e88d857b7d016614da28ee853ac79474589688c89796246e4ced8ad1a51a04f2e4d67fc6d815a1912778804464c13c470a2f4a5099d06ac0b829c38b14251ca33b010479a6fdc8910a015e69;
Z=0x23b86fb03f1497f6857a932d1fc76a9ace84c4202ec7e9fd019889552c2ac2a317777fa99faa05974394455730eb051552bc16457dedbc974c8c6bce2acb4876a7ea352cadb826fa4ca2e9da6e3a0b4f166ff771fe6aad5a6229e3a8b2c9a1d2e75fa0346974ef277e5eac17262f49b6e;
A=0xa3a7890d600eca23d397105f3149a34128abf731ea39b8fe3c88b09b4a2e457b680a8a556c221d183d6f2b58b8e1b8bf96e64b1475be37a87da1c537a1eb541a024e866b92e050cdfed7bcda31570d43f6fdccfbbcdadb4a9d86a5a05565911336cdbc2f2ec93d3c5da6d0a63ecdd64a9;

When resuming from a checkpoint the wrapper should invoke ecm with the -resume option like:

Code: Alles auswählen

ecm -resume checkpnt 25e9

[brianscott]

Auto-update rebooted my computer and all started over now.

[Michael H.W. Weber]

Auto-update rebooted my computer and all started over now.

That is the expected behavior and one of the reasons why autoupdate should be deactivated: Never let a machine decide.

Michael.

[emmascott63]

Thanks for all the insights everyone.
It’s clear now that the wrapper doesn't always resume properly even though GMP-ECM does support checkpointing. It’s a bit disappointing that after 2–3 days of CPU time, everything can restart just because of an auto-update reboot.
I’ll definitely disable automatic updates from now on to avoid losing progress. Still, I wonder if there’s a way to manually trigger the ECM executable with the -resume option using the saved checkpnt file — or if the wrapper prevents that level of control?

[Daisy Holland]

Hey Boinc'er! Those initial BOINC estimates can be a bit off sometimes, especially early on. Your 8-9 day estimate sounds much more realistic given the progress so far. Just keep an eye on it, and if you see it consistently trending longer, you might want to check your system resources are allocated properly. Hopefully it finishes within your projected timeframe – maybe treat yourself to a Sprunki when it's done as a reward! Good luck with the computation!