PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise

Advanced search

Message boards : Problems and Help : Primegrid returning incorrect run/cpu time

Author Message
Joby Kechinsky
Send message
Joined: 1 Sep 20
Posts: 20
ID: 1300456
Credit: 2,168,091
RAC: 14,544
PPS LLR Gold: Earned 500,000 credits (581,926)SoB LLR Gold: Earned 500,000 credits (645,570)PPS Sieve Silver: Earned 100,000 credits (185,405)AP 26/27 Bronze: Earned 10,000 credits (92,989)GFN Gold: Earned 500,000 credits (647,762)WW Bronze: Earned 10,000 credits (12,000)
Message 145884 - Posted: 30 Nov 2020 | 15:40:28 UTC
Last modified: 30 Nov 2020 | 15:42:33 UTC

For some time now I have been running PPS-MEGA tasks on my computer which usually take 65-95 minutes to run on two CPUs. However, when I checked my completed workunits over the past week or so, I noticed several workunits with runtime of 20 minutes, or even as low as 5 minutes. These are full-length tasks (43k+ gflops), and not short DC tasks.

Upon further investigation, I realised that when my computer goes to sleep after several minutes of inactivity, the computing will cease. When I restart my computer, the run time is reset, so if the task has been running for an hour before the computer goes to sleep, and after restarting takes another 5 minutes to complete, the run time will be reported as 5 minutes, instead of the accurate value of 65 minutes.

I just want to check if this may cause any problems with the prime finding? If the first 60 minutes of work are not recorded, may this error cause the programme to miss any primes?

Profile Rick Reynolds
Avatar
Send message
Joined: 13 Aug 10
Posts: 8159
ID: 65483
Credit: 6,711,806,271
RAC: 42,466
Discovered 3 mega primesFound 2 primes in the 2018 Tour de PrimesFound 2 primes in the 2019 Tour de PrimesFound 12 primes in the 2020 Tour de PrimesFound 2 primes in the 2021 Tour de PrimesFound 1 mega prime in the 2021 Tour de Primes321 LLR Jade: Earned 10,000,000 credits (10,244,909)Cullen LLR Jade: Earned 10,000,000 credits (10,194,451)ESP LLR Turquoise: Earned 5,000,000 credits (9,516,673)Generalized Cullen/Woodall LLR Jade: Earned 10,000,000 credits (10,216,354)PPS LLR Emerald: Earned 50,000,000 credits (73,178,392)PSP LLR Turquoise: Earned 5,000,000 credits (5,151,448)SoB LLR Jade: Earned 10,000,000 credits (10,045,557)SR5 LLR Jade: Earned 10,000,000 credits (14,871,275)SGS LLR Turquoise: Earned 5,000,000 credits (7,860,522)TRP LLR Jade: Earned 10,000,000 credits (11,130,742)Woodall LLR Turquoise: Earned 5,000,000 credits (5,419,909)321 Sieve (suspended) Double Bronze: Earned 100,000,000 credits (101,538,236)Cullen/Woodall Sieve (suspended) Double Bronze: Earned 100,000,000 credits (127,922,665)Generalized Cullen/Woodall Sieve (suspended) Sapphire: Earned 20,000,000 credits (30,984,158)PPS Sieve Double Ruby: Earned 2,000,000,000 credits (2,840,173,136)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Turquoise: Earned 5,000,000 credits (8,134,964)TRP Sieve (suspended) Turquoise: Earned 5,000,000 credits (7,013,696)AP 26/27 Double Silver: Earned 200,000,000 credits (276,723,135)GFN Double Silver: Earned 200,000,000 credits (349,277,565)WW Double Amethyst: Earned 1,000,000,000 credits (1,431,508,000)PSA Double Amethyst: Earned 1,000,000,000 credits (1,370,700,486)
Message 145885 - Posted: 30 Nov 2020 | 15:50:52 UTC - in response to Message 145884.

For some time now I have been running PPS-MEGA tasks on my computer which usually take 65-95 minutes to run on two CPUs. However, when I checked my completed workunits over the past week or so, I noticed several workunits with runtime of 20 minutes, or even as low as 5 minutes. These are full-length tasks (43k+ gflops), and not short DC tasks.

Upon further investigation, I realised that when my computer goes to sleep after several minutes of inactivity, the computing will cease. When I restart my computer, the run time is reset, so if the task has been running for an hour before the computer goes to sleep, and after restarting takes another 5 minutes to complete, the run time will be reported as 5 minutes, instead of the accurate value of 65 minutes.

I just want to check if this may cause any problems with the prime finding? If the first 60 minutes of work are not recorded, may this error cause the programme to miss any primes?

There are folks that have a lot more knowledge about this but a couple of things. 1) if you allow your pc to sleep/hibernate and it stops running the task(s) until you wake it back up your chances of being the initial prime finder go way down and 2) when it resumes should pick up where it left off or close to it and as long as it is finished in a valid state will count regardless of the "stats" on runtime.

Cheers Rick

Profile Michael GoetzProject donor
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 21 Jan 10
Posts: 13646
ID: 53948
Credit: 285,191,351
RAC: 56,925
The "Shut up already!" badge:  This loud mouth has mansplained on the forums over 10 thousand times!  Sheesh!!!Discovered the World's First GFN-19 prime!!!Discovered 1 mega primeFound 1 prime in the 2018 Tour de PrimesFound 1 prime in the 2019 Tour de PrimesFound 1 prime in the 2020 Tour de PrimesFound 2 primes in the 2021 Tour de Primes321 LLR Turquoise: Earned 5,000,000 credits (5,132,712)Cullen LLR Turquoise: Earned 5,000,000 credits (5,038,114)ESP LLR Turquoise: Earned 5,000,000 credits (6,177,890)Generalized Cullen/Woodall LLR Ruby: Earned 2,000,000 credits (2,213,035)PPS LLR Sapphire: Earned 20,000,000 credits (20,751,038)PSP LLR Turquoise: Earned 5,000,000 credits (7,956,186)SoB LLR Sapphire: Earned 20,000,000 credits (36,067,618)SR5 LLR Jade: Earned 10,000,000 credits (10,007,110)SGS LLR Ruby: Earned 2,000,000 credits (3,718,606)TRP LLR Turquoise: Earned 5,000,000 credits (5,084,329)Woodall LLR Ruby: Earned 2,000,000 credits (4,982,922)321 Sieve (suspended) Jade: Earned 10,000,000 credits (10,061,196)Cullen/Woodall Sieve (suspended) Ruby: Earned 2,000,000 credits (4,170,256)Generalized Cullen/Woodall Sieve (suspended) Turquoise: Earned 5,000,000 credits (5,059,304)PPS Sieve Sapphire: Earned 20,000,000 credits (22,885,121)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Amethyst: Earned 1,000,000 credits (1,035,522)TRP Sieve (suspended) Ruby: Earned 2,000,000 credits (2,051,121)AP 26/27 Jade: Earned 10,000,000 credits (10,118,303)GFN Emerald: Earned 50,000,000 credits (78,031,938)WW Sapphire: Earned 20,000,000 credits (32,204,000)PSA Jade: Earned 10,000,000 credits (12,445,029)
Message 145886 - Posted: 30 Nov 2020 | 15:54:52 UTC - in response to Message 145885.

For some time now I have been running PPS-MEGA tasks on my computer which usually take 65-95 minutes to run on two CPUs. However, when I checked my completed workunits over the past week or so, I noticed several workunits with runtime of 20 minutes, or even as low as 5 minutes. These are full-length tasks (43k+ gflops), and not short DC tasks.

Upon further investigation, I realised that when my computer goes to sleep after several minutes of inactivity, the computing will cease. When I restart my computer, the run time is reset, so if the task has been running for an hour before the computer goes to sleep, and after restarting takes another 5 minutes to complete, the run time will be reported as 5 minutes, instead of the accurate value of 65 minutes.

I just want to check if this may cause any problems with the prime finding? If the first 60 minutes of work are not recorded, may this error cause the programme to miss any primes?

There are folks that have a lot more knowledge about this but a couple of things. 1) if you allow your pc to sleep/hibernate and it stops running the task(s) until you wake it back up your chances of being the initial prime finder go way down and 2) when it resumes should pick up where it left off or close to it and as long as it is finished in a valid state will count regardless of the "stats" on runtime.

Cheers Rick


With LLR2, you don't have to worry about being "the prime finder". :)

But Rick is correct that the task will complete correctly.

BOINC sometimes has trouble keeping its timing values straight when BOINC is shut down and restarts. It won't hurt anything, so you don't need to worry about it.
____________
My lucky number is 75898524288+1

Profile Rick Reynolds
Avatar
Send message
Joined: 13 Aug 10
Posts: 8159
ID: 65483
Credit: 6,711,806,271
RAC: 42,466
Discovered 3 mega primesFound 2 primes in the 2018 Tour de PrimesFound 2 primes in the 2019 Tour de PrimesFound 12 primes in the 2020 Tour de PrimesFound 2 primes in the 2021 Tour de PrimesFound 1 mega prime in the 2021 Tour de Primes321 LLR Jade: Earned 10,000,000 credits (10,244,909)Cullen LLR Jade: Earned 10,000,000 credits (10,194,451)ESP LLR Turquoise: Earned 5,000,000 credits (9,516,673)Generalized Cullen/Woodall LLR Jade: Earned 10,000,000 credits (10,216,354)PPS LLR Emerald: Earned 50,000,000 credits (73,178,392)PSP LLR Turquoise: Earned 5,000,000 credits (5,151,448)SoB LLR Jade: Earned 10,000,000 credits (10,045,557)SR5 LLR Jade: Earned 10,000,000 credits (14,871,275)SGS LLR Turquoise: Earned 5,000,000 credits (7,860,522)TRP LLR Jade: Earned 10,000,000 credits (11,130,742)Woodall LLR Turquoise: Earned 5,000,000 credits (5,419,909)321 Sieve (suspended) Double Bronze: Earned 100,000,000 credits (101,538,236)Cullen/Woodall Sieve (suspended) Double Bronze: Earned 100,000,000 credits (127,922,665)Generalized Cullen/Woodall Sieve (suspended) Sapphire: Earned 20,000,000 credits (30,984,158)PPS Sieve Double Ruby: Earned 2,000,000,000 credits (2,840,173,136)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Turquoise: Earned 5,000,000 credits (8,134,964)TRP Sieve (suspended) Turquoise: Earned 5,000,000 credits (7,013,696)AP 26/27 Double Silver: Earned 200,000,000 credits (276,723,135)GFN Double Silver: Earned 200,000,000 credits (349,277,565)WW Double Amethyst: Earned 1,000,000,000 credits (1,431,508,000)PSA Double Amethyst: Earned 1,000,000,000 credits (1,370,700,486)
Message 145887 - Posted: 30 Nov 2020 | 15:57:44 UTC - in response to Message 145886.

With LLR2, you don't have to worry about being "the prime finder". :)

Man I keep forgetting about that super cool change !!

stream
Volunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 919
ID: 301928
Credit: 513,274,703
RAC: 5,007
Discovered 1 mega primeFound 1 prime in the 2018 Tour de PrimesFound 1 prime in the 2019 Tour de PrimesFound 1 prime in the 2020 Tour de PrimesFound 1 prime in the 2021 Tour de Primes321 LLR Jade: Earned 10,000,000 credits (10,011,570)Cullen LLR Jade: Earned 10,000,000 credits (10,009,374)ESP LLR Jade: Earned 10,000,000 credits (10,009,221)Generalized Cullen/Woodall LLR Jade: Earned 10,000,000 credits (10,012,217)PPS LLR Jade: Earned 10,000,000 credits (16,277,057)PSP LLR Jade: Earned 10,000,000 credits (10,044,081)SoB LLR Jade: Earned 10,000,000 credits (10,064,750)SR5 LLR Jade: Earned 10,000,000 credits (10,002,051)SGS LLR Jade: Earned 10,000,000 credits (10,001,295)TRP LLR Jade: Earned 10,000,000 credits (10,002,411)Woodall LLR Jade: Earned 10,000,000 credits (10,013,921)321 Sieve (suspended) Sapphire: Earned 20,000,000 credits (20,004,228)Generalized Cullen/Woodall Sieve (suspended) Sapphire: Earned 20,000,000 credits (20,047,667)PPS Sieve Sapphire: Earned 20,000,000 credits (20,866,490)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Sapphire: Earned 20,000,000 credits (20,043,271)TRP Sieve (suspended) Sapphire: Earned 20,000,000 credits (20,015,177)AP 26/27 Sapphire: Earned 20,000,000 credits (20,045,194)GFN Emerald: Earned 50,000,000 credits (55,355,287)WW Sapphire: Earned 20,000,000 credits (20,148,000)PSA Double Silver: Earned 200,000,000 credits (200,301,443)
Message 145963 - Posted: 1 Dec 2020 | 14:03:45 UTC

It can be small problem in wrapper which should be fixed in upcoming LLR2 software update (there are 5 different types of checkpoint files in LLR2, not all of them were handled correctly).

Anyway, this is purely cosmetic problem. Reported runtime is not used anywhere except some statistic (which never wasn't accurate - task runtime often resets after crashes or reboots).

Post to thread

Message boards : Problems and Help : Primegrid returning incorrect run/cpu time

[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2021 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 1.77, 1.85, 1.76
Generated 17 Sep 2021 | 3:03:16 UTC