PrimeGrid
Please visit donation page to help the project cover running costs for this month
1) Message boards : Number crunching : Updated BOINC Clients (Message 140493)
Posted 487 days ago by Omega
Which version *exactly* was this change implemented?


For me, it happened after I updated 7.9 to 7.16.
2) Message boards : Number crunching : Bad luck club (Message 140277)
Posted 500 days ago by Omega
50.000 (yup, fifty-thousand) GFN-15 tasks and still... nada, niente, nichts, nothing!
Thank you PG-server for allowing me to reach this record of unluckiness.
3) Message boards : Number crunching : Bad luck club (Message 140078)
Posted 513 days ago by Omega
Following the old saying 'misery loves company' this thread is a place for crunchers to share their bad luck stories, i.e. large number of tasks in a subproject without a hit.

Number of tasks should exceed 2*(server-average+10%)
[Server-average = Subproject status -> Completed/Primes]
[+10% is to compensate for increasing number size]

My bad luck subproject is GFN-15:
I am at approximately 40.000 tasks without a hit, which is almost five times the server average (7685*1.1=8454).
4) Message boards : Number crunching : Updated BOINC Clients (Message 139551)
Posted 537 days ago by Omega
After upgrading my BOINC client is pre-fetching work (downloading a new WU when the current one is at ~90%) even though "resource share" and "maintain enough work for" is both set to zero.
Anybody else experience this? Any way to disable that?

It is lesson for next time: dont update if not broken :)


That's really helpful, thanks...

Anyway, I am seeing a slight speed increase since upgrading (not sure why) so it was worth it.
And limiting "max # PG tasks" works as a temporary workaround for the pre-fetch-bug.
But if anybody has an idea how to fix that issue I'd appreciate it.
5) Message boards : Number crunching : Updated BOINC Clients (Message 139547)
Posted 537 days ago by Omega
After upgrading my BOINC client is pre-fetching work (downloading a new WU when the current one is at ~90%) even though "resource share" and "maintain enough work for" is both set to zero.
Anybody else experience this? Any way to disable that?
6) Message boards : Number crunching : Year-long Tour de Primes (Message 139078)
Posted 556 days ago by Omega
Ever wonder what the results of a year-long TdP would be?
Here are the "unofficial" results of the year 2019:
(Just like in the official TdP only primes large enough for T5K were counted.)

Total primes found: 815
Total prime score: 780,568.329
Total number of users who found at least one prime: 237

Red Jersey (largest prime)
#1 Penguin: 99739*2^14019102+1 (ESP; 4,220,176 digits)
#2 tng*: 2805222*25^2805222+1 (GCW; 3,921,539 digits)
#3 Freezing: 3214654^524288+1 (GFN19; 3,411,613 digits)

Yellow Jersey (prime count)
#1 Randall J. Scalise: 39 primes found
#2 CGB: 35
#3 Scott Brown: 33

Green Jersey (prime score)
#1 Penguin: 99,903.956
#2 tng*: 84,506.967
#3 Freezing: 52,563.826
7) Message boards : Number crunching : 2020 Mega Primes (Message 139075)
Posted 556 days ago by Omega
I made a chart of mega primes prime-score by year (stacked by projects).
Unfortunately, I haven't found a way to embed the chart in a forum post.
[Side-question: Is it possible to embed content in forum posts via "[iframe]"?]
But here's the link for those interested:
Link to interactive chart
8) Message boards : Number crunching : Tour de Primes 2020 (Message 137873)
Posted 592 days ago by Omega
Wow! 23 megaprimes found so far and it's only Feb 14th...
9) Message boards : Number crunching : Tour de Primes 2020 (Message 137554)
Posted 598 days ago by Omega
You know, I kind of wish it was. And I imagine it could be. The server could be set to send double-checks, say, 1 day later. Maybe 1 hour for tests faster than PPS? Then we could all abandon this multithreading stuff and we'd probably find more primes overall.

You'd have to randomize WU names (_1 vs. _0); otherwise somebody would just abort all the _1's. ;) I think the biggest problem aside from fiddling with the scheduler would be DB usage going up. But it might be possible.


I absolutely love that idea! It would give everyone (regardless of hardware etc.) an equal chance of being first.

The only drawbacks of this I can think of would be a) elimination of the "race to be first" b) increased database c) longer turnaround for WU's.

But IMO these downsides are outweighed by the overall increase to fairness especially for users with older/slower host.
10) Message boards : Number crunching : Prime score by credit (Message 137394)
Posted 599 days ago by Omega
@Nick: The figures you posted are Primes/Tasks which is precisely the metric I am "criticizing". But I took the trouble and calculated your current credit/prime_score:
PPS: 10458.10 C/PS
GFN: 79196.17 C/PS
SGS: 5257.26 C/PS

To avoid confusion here's how I got to these figures:
In PPS you have a prime score of 856.315 and credit of 8955431, 8955431/856.315 = 10458.10 C/PS


Next 10 posts
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2021 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 3.55, 3.83, 3.59
Generated 29 Sep 2021 | 1:26:55 UTC