Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Number crunching :
Makar Sankranti Challenge
| Author |
Message |
|---|
|
|
|
Welcome to the Makar Sankranti Challenge
Makar Sankranti is a Hindu festival celebrated in almost all parts of India and Nepal in a myriad of cultural forms. Makar Sankranti marks the transition of the Sun into the zodiac sign of Makara rashi (Capricorn) on its celestial path. The day is also believed to mark the arrival of spring in India and is a traditional event. Makara Sankranthi is a solar event making one of the few Indian festivals which fall on the same date in the Gregorian calendar every year: 14 January, with some exceptions when the festival is celebrated on 13 or 15 January.
To warm up for this festival PrimeGrid is offering a an 8 day challenge on some of Generalized Fermat Number prime search. From January 7th 18:00:00 UTC until January 15th 18:00:00 UTC we will have an 8 day challenge running several Generalized Fermat Prime Search Projects.
These GFN-projects are part of the challenge:
GFN-17 MEGA
GFN-18
GFN-19
GFN-20
GFN-21
GFN-WR
These GFN-projects are NOT part of the challenge:
GFN-15
GFN-16
GFN-17 LOW
Important: The deadline for some of these WUs is significantly longer than eight days, so make sure your computer returns the WUs before the end of the challenge.
Application Builds
IMPORTANT: Overclocking -- including factory overclocking -- on Nvidia GPUs is very strongly discouraged. Even if your GPU can run other tasks without difficulty, it may be unable to run GFN tasks when overclocked.
We now have nine different GFN searches running. This post provides details about what's being searched.
GFNs can be searched by both CPUs and GPUs. There's several variations of both the CPU and GPU transforms which vary greatly by speed and b-limits. CPU transforms come in two flavors:
- 64 bit: This includes the default, SSE2, SSE4, AVX-INTEL, AVX-AMD, FMA3, and FMA4 transforms. The fastest available transform is selected automatically by the CPU app.
- 80 bit: This is the x87 transform. It has a very high b-limit, but is much slower than the 64 bit transforms.
A single CPU app (for each platform) is used that can run all of the transforms.
Note that both 64 bit and 80 bit transforms will run on both 32 bit and 64 bit CPUs.
GPU transforms come in 4 varieties:
- CUDA: This has the lowest b-limit, but the limit is only slightly lower than OCL's limit. CUDA is usually a bit slower than OCL, but it uses almost no CPU. All of the OCL transforms use a full CPU core to service the GPU.
- Requires a GPU with double precision hardware.
- OCL: This is usually faster than CUDA, and has a slightly higher b-limit.
- Requires a GPU with double precision hardware.
- OCL3: OCL3 is usually slower -- often significantly slower -- than OCL, but runs particularly well on Maxwell-architecture Nvidia GPUs, where it is usually faster than OCL. OCL3 has a much higher b-limit than either CUDA or OCL.
- OCL3 does NOT require a GPU with double precision hardware.
- OCL2: OCL2 is the GPU equivalent of the 80-bit x87 transform on CPUs. It has a very high b-limit, but is much slower than the other GPU transforms.
- OCL2 does NOT require a GPU with double precision hardware.
- On an Nvidia GPU, CC 2.0 (Compute Capability) is required. This generally means at least a GTX 4xx series GPU, although there are some exceptions. If you're not sure, you can check on Nvidia's CUDA GPU list and Nvidia's Legacy CUDA GPU list. There's no restriction on ATI/AMD GPUs.
- Due to a driver bug, OCL2 is not available on ATI/AMD GPUs running on Mac computers.
Currently there is a separate app for each GPU transform, although we plan on combining the three OCL transforms into a single app.
A Cautionary Reminder
ATTENTION: The primality programs GeneferCUDA and GeneferOCL (both GPU and CPU) are computationally intensive; so, it is vital to have a stable system with good cooling. It does not tolerate "even the slightest of errors." Please see this post for more details on how you can "stress test" your CPU, and please see this post for tips on running GFN on your GPU successfully.
As with all number crunching, excessive heat can potentially cause permanent hardware failure. Please ensure your cooling system is sufficient.
If you're using an Nvidia GPU and have never run GeneferCUDA before, please read these tips. GeneferCUDA stresses a GPU more than any other program I've seen and is incredibly intolerant of overclocking. It is strongly suggested that you run at least one (Short) Work Unit before the challenge to make sure your computer can handle it. Note that "Overclocking" includes GPUs that come overclocked from the factory, and lowering clock rates to the reference speeds is sometimes necessary. In the case of one particular GPU, the GTX 550 Ti, lowering the memory clock below the reference speed is often necessary.
WR WU's will take about 5 days on a GTX 580 GPU. A GTX 680 will be slower than a GTX 580 for this application. On my computer (GTX 460 & C2D Q6600), which is more of an "average" computer and certainly not the fastest, a Work Unit takes about 12 days on the GPU. For a general idea of how your GPU stacks up, you can have a look at the fastest gpu list
If your CPU is highly overclocked, please consider "stress testing" it. Overclocking your GPU is not recommended at all for GeneferCUDA. Sieving is an excellent alternative for computers that are not able to run Genefer. :)
Please, please, please make sure your machines are up to the task.
Time zone converter:
The World Clock - Time Zone Converter
NOTE: The countdown clock on the front page uses the host computer time. Therefore, if your computer time is off, so will the countdown clock. For precise timing, use the UTC Time in the data section to the left of the countdown clock.
Scoring information
Scores will be kept for individuals and teams. Only work units issued AFTER January 7th 18:00:00 UTC and received BEFORE January 15th 18:00:00 UTC will be considered for credit.
In this challenge we will be using the same scoring algorithm as we use to determine BOINC credits, including bonuses!. Because the score bonuses are included in the challenge score, it is advantageous to run the longer tasks if you can manage to finish them within the 8 day challenge window. This will land you a higher position in the leaderboard and therefor a higher score on the overal leaderboard.
What to expect at Challenge start
The server always gets hit hard at the beginning of the Challenge. However, GFN tasks are quite long so we don't expect a heavy load. Nevertheless, a few hours before the start "max cache" will be dropped. Additionally, "max to send" will be dropped. Anyone attempting to request more will be met with "max cache" messages.
We'll raise the front page buffer before the start of the Challenge. These settings will be adjusted as necessary. Afterwards, as conditions allow, we'll raise "max cache". We'll continue to increase "max cache" when the server can handle it.
This method allows the greatest opportunity for the most clients to get work. Even if it's just 1 task for the first few minutes, at least the client is crunching. Past Challenges have shown that clients have an excellent chance to reach "max cache" before their first task is complete. We expect the same this time.
Strategies for starting the Challenge
Depending on a variety of factors, different strategies work for different users. Here are just a few to consider:
- large farm, user can be present at start
-Set Computer is connected to the Internet about every to 0 days
-Set Maintain enough work for an additional to 0 days
-Change PrimeGrid preferences to a fast WU project such as PPSE (LLR)
-At Challenge start, update PrimeGrid preferences and only select the GFN World Record project
-At worse, you'll only be 1 PPSE (LLR) WU late on each core starting the Challenge.
-After all machines have work, increase Maintain enough work for an additional buffer
- large farm, user NOT able to be present at start
-Same connection settings as above
-At earliest access to hosts after start, switch to the GFN (World Record) project
- a few computers, user can be present at start
-Change PrimeGrid preferences and only select the GFN (World record) project
-Set computers to "No New Tasks" for PrimeGrid
-At Challenge Start, update computers to "Allow New Tasks"
- a few computers, user NOT able to be present at start
-same settings as "large farm, user NOT able to be present at start"
NOTE: This presumes you have all other BOINC projects suspended.
At the Conclusion of the Challenge
We kindly ask users "moving on" to ABORT their WU's instead of DETACHING, RESETTING, or PAUSING.
ABORTING WU's alows them to be recycled immediately; thus a much faster "clean up" to the end of a challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.
Please consider either completing what's in the queue or ABORTING them. Thank you. :)
For those of you who wish to continue to help with GFN sieving, we are still sieving n=22 (World Record Units), as well as the n=20 (short) range and n=21 (next short) range. Please see We need your help with GFN Sieving! for more information.
More information on Generalized Fermat Numbers and the Genefer program
Best of Luck to everyone!
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
| |
|
 RafaelVolunteer tester
Send message
Joined: 22 Oct 14
Posts: 909
ID: 370496
Credit: 529,897,285
RAC: 383,035
                        
|
|
Wait a minute, GFN-17 Mega uses OCL2, and n=18~20 are using OCL3, neither of which requires double precision hardware to work! | |
|
|
|
Wait a minute, GFN-17 Mega uses OCL2, and n=18~20 are using OCL3, neither of which requires double precision hardware to work!
Fixed a couple of mistakes, including this one.
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
| |
|
Michael Goetz Volunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
                         
|
|
A few notes about this challenge. There's 6 different projects that are part of this challenge, and they're all a little bit different:
- All of these tasks are on numbers larger than one million digits, so any primes found will be mega-primes.
- The best chance for finding a prime is with the GFN-17-Mega tasks. That's the smallest numbers, so primes are more likely, and the tasks also are the fastest, so you can do more tests.
- GFN-19 has the best chance of finding the largest known GFN prime.
- Any prime found on GFN-20, GFN-21, or GFN-22 would be the first known GFN prime at those respective bases.
- A prime found with GFN-22 would be the world's largest known prime of any kind.
- GFN-22 will produce challenge points fastest -- it has a significant bonus and the b values are small enough so that the most efficient CPU and GPU transforms can be used. However, these tasks are huge and you need a fairly fast GPU to complete one in less than 8 days. No CPU can complete these tasks quick enough for the challenge.
- On most CPUs, the most efficient CPU transforms will be used on GFN-19, 20, 21, and 22.
- On most GPUs, the most efficient GPU transform will be used on GFN-21 and 22.
- Nvidia Maxwell GPUs may benefit from using app_info to run OCL3 instead of OCL on GFN-21 and 22.
- GPUs except Nvidia Maxwell GPUs may benefit by using OCL4 instead of OCL3 on GFN-18, 19, and 20.
- For all GFN projects, the Windows OCL apps on Nvidia GPUs will use as much as a full CPU core. Where available (GFN-21 and 22 only, for Nvidia GPUs), CUDA will use much less CPU, but it's slower than OCL. (I'm not sure if this is true for Linux/Mac, or ATI/AMD GPUs.)
- OCL2 (used for GFN-17-Mega), requires CC 2.0 or above if you're using an Nvidia GPU. Furthermore, OCL2 is unfortunately not available for ATI/AMD GPUs running on Mac computers.
- Finally, some newer ATI/AMD GPUs may not be recognized by the server and require using app_info to work.
If you're not familiar with the different GFN projects, the characteristics of each one are described in this forum post. Note that the first three projects listed (GFN-15, GFN-16, and GFN-17-LOW) are NOT part of this challenge.
____________
My lucky number is 75898524288+1
| |
|
|
|
|
The results of the test on the configuration:
CPU: Intel Core i5-4690K @ 4,6GHz
Graphic Cards: Inno3D iChill GeForce GTX 770 HerculeZ X3 Ultra 2 GB (1150 / 1254Boost / 7200)
Tasks: GFN15
Only CPU: 4 tasks on 810 seconds.
Only GPU: 1 task 142 seconds.
CPU + GPU: CPU task 4 from 816 to 1100 seconds; GPU on one task spends 160-190 seconds.
| |
|
|
|
The results of the test on the configuration:
CPU: Intel Core i5-4690K @ 4,6GHz
Graphic Cards: Inno3D iChill GeForce GTX 770 HerculeZ X3 Ultra 2 GB (1150 / 1254Boost / 7200)
Tasks: GFN15
Only CPU: 4 tasks on 810 seconds.
Only GPU: 1 task 142 seconds.
CPU + GPU: CPU task 4 from 816 to 1100 seconds; GPU on one task spends 160-190 seconds.
Please note that these are not part of the challenge.
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Oddly enough, I'm planning on running all of the different GFN sub projects that are part of this challenge. My goal is to earn the most amount of challenge points possible with the hardware I have.
On my old 32 bit CPU I'll be running 17-Mega. (It only has x87 and default transforms available, and it's too slow to finish the larger tasks in 8 days. Might as well run the smallest available task.)
On the i5, I'll run one set of GFN-21s, followed by 2 sets of 20s, and will finish with 19s. (19 is the smallest task that can run FMA3 right now, so I don't want to run 18 or 17-mega. 21 and 20 have credit bonuses, so they're preferable.)
The GPU will probably have time to run 1 WR, then 3 21s, a 20, and will finish doing 18s. (WR uses the fastest transform and has the largest bonus. 21 also uses the fastest transform and has the second highest bonus. 20 uses a slower transform, but also has a bonus. Finally, 18 is the smallest task that doesn't use the OCL2 (slowest) transform.)
This is based upon getting the most out of the credit bonuses and fastest transforms and the expected run times of each task.
Of course, my timings are based on a "single-core" tests, so they're overly optimistic. I'll need to adjust the plan on the fly. But right now, it looks like the optimal plan involves running at least one of each type of task.
____________
My lucky number is 75898524288+1 | |
|
|
|
Makar Sankranti marks the transition of the Sun into the zodiac sign of Makara rashi (Capricorn) on its celestial path.
In case someone wonders (like I did) why this would happen at January 14 (approx.), when in the "usual" western astrology we say Capricorn (the mountain goat) starts at December 21 (approx.), the explanation is that Hindu astrology uses a sidereal zodiac while the West uses a tropical zodiac.
In fact, the Hindus have Makara rashi (Capricorn) when the Sun is actually among the stars which make up the constellation (star configuration) representing the goat (Capricorn).
/JeppeSN
| |
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2639
ID: 29980
Credit: 568,393,769
RAC: 2,469
                   
|
On the i5, I'll run one set of GFN-21s, followed by 2 sets of 20s, and will finish with 19s. (19 is the smallest task that can run FMA3 right now, so I don't want to run 18 or 17-mega. 21 and 20 have credit bonuses, so they're preferable.)
Of course, my timings are based on a "single-core" tests, so they're overly optimistic. I'll need to adjust the plan on the fly. But right now, it looks like the optimal plan involves running at least one of each type of task.
I did some 4 instance testing on my fastest (i7-6700k) system earlier. I was a bit surprised to find 19 and 20 about the same in credits per hour, with 20 about 3% higher. 21 saw that drop to 10% below 19. Think it is the old units tripping over themselves again. Now what I didn't do was test run 3 units since I was going to leave a core free for the much faster GPU... maybe reduced demand for shared resources will allow 21 to pick up, but I think I'm out of time for more practical testing. | |
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 938
ID: 3110
Credit: 258,708,411
RAC: 92,597
                
|
Currently there is a separate app for each GPU transform, although we plan on combining the three OCL transforms into a single app.
I'm confused. I only see a single "OpenCL" checkbox. And I only see one OpenCL app per project on the Applications page. So how do I select an app? Or is it associated with a WU? Or did you already do the combining?
____________
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
Currently there is a separate app for each GPU transform, although we plan on combining the three OCL transforms into a single app.
I'm confused. I only see a single "OpenCL" checkbox. And I only see one OpenCL app per project on the Applications page. So how do I select an app? Or is it associated with a WU? Or did you already do the combining?
You don't. There's only one OCL app for each sub-project.
If you want to run a different OCL version, you need to set it up with app_info.
When you select OCL, you get the original OCL for 21 and 22 (WR), OCL2 for 15 and 17-Mega, and OCL3 for 16, 17-Low, 18, 19, and 20. For most GPU types, that's the fastest version of OCL for each sub-project. OCL4 isn't included because it is brand new and still experimental and evolving.
____________
My lucky number is 75898524288+1 | |
|
|
|
OCL4 isn't included because it is brand new and still experimental and evolving.
That's too bad as from what I've read on the posts this version (OCL4 new) is pretty fast and efficient.
Cheers | |
|
RafaelVolunteer tester
Send message
Joined: 22 Oct 14
Posts: 909
ID: 370496
Credit: 529,897,285
RAC: 383,035
|
OCL4 isn't included because it is brand new and still experimental and evolving.
That's too bad as from what I've read on the posts this version (OCL4 new) is pretty fast and efficient.
Cheers
We"re just waiting Yves aproval to stary the testing on actual WUs :) | |
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 938
ID: 3110
Credit: 258,708,411
RAC: 92,597
|
|
We're off!
And this is strange. I'm running 3 WUs, all "18"s, on one machine:
This one's done about .5%.
This one's done about .5%.
This one's done about 2.7%!
Any idea why that one is so much faster?
____________
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Good luck everyone!
This is what's been sent out over the first 20 minutes:
Challenge: Makar Sankranti
App: 25 (GFN-17-Mega)
(As of 2016-01-07 18:20:14 UTC)
2915 tasks have been sent out. [CPU/GPU/anonymous_platform: 1807 (62%) / 1103 (38%) / 5 (0%)]
Of those tasks that have been sent out:
14 (0%) came back with some kind of an error. [0 (0%) / 14 (0%) / 0 (0%)]
0 (0%) have returned a successful result. [0 (0%) / 0 (0%) / 0 (0%)]
2901 (100%) are still in progress. [1807 (62%) / 1089 (37%) / 5 (0%)]
Of the tasks that have been returned successfully:
0 (0%) are pending validation. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=42817946. The leading edge was at b=42809588 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.02% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 26 (GFN-18)
(As of 2016-01-07 18:20:14 UTC)
943 tasks have been sent out. [CPU/GPU/anonymous_platform: 392 (42%) / 548 (58%) / 3 (0%)]
Of those tasks that have been sent out:
9 (1%) came back with some kind of an error. [1 (0%) / 8 (1%) / 0 (0%)]
0 (0%) have returned a successful result. [0 (0%) / 0 (0%) / 0 (0%)]
934 (99%) are still in progress. [391 (41%) / 540 (57%) / 3 (0%)]
Of the tasks that have been returned successfully:
0 (0%) are pending validation. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=1303422. The leading edge was at b=1301204 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.17% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 27 (GFN-19)
(As of 2016-01-07 18:20:14 UTC)
991 tasks have been sent out. [CPU/GPU/anonymous_platform: 673 (68%) / 299 (30%) / 19 (2%)]
Of those tasks that have been sent out:
11 (1%) came back with some kind of an error. [0 (0%) / 11 (1%) / 0 (0%)]
0 (0%) have returned a successful result. [0 (0%) / 0 (0%) / 0 (0%)]
980 (99%) are still in progress. [673 (68%) / 288 (29%) / 19 (2%)]
Of the tasks that have been returned successfully:
0 (0%) are pending validation. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=942594. The leading edge was at b=939956 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.28% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 28 (GFN-20)
(As of 2016-01-07 18:20:15 UTC)
565 tasks have been sent out. [CPU/GPU/anonymous_platform: 414 (73%) / 114 (20%) / 37 (7%)]
Of those tasks that have been sent out:
10 (2%) came back with some kind of an error. [9 (2%) / 1 (0%) / 0 (0%)]
0 (0%) have returned a successful result. [0 (0%) / 0 (0%) / 0 (0%)]
555 (98%) are still in progress. [405 (72%) / 113 (20%) / 37 (7%)]
Of the tasks that have been returned successfully:
0 (0%) are pending validation. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=728684. The leading edge was at b=727428 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.17% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 16 (GFN-21)
(As of 2016-01-07 18:20:15 UTC)
190 tasks have been sent out. [CPU/GPU/anonymous_platform: 69 (36%) / 118 (62%) / 3 (2%)]
Of those tasks that have been sent out:
1 (1%) came back with some kind of an error. [0 (0%) / 1 (1%) / 0 (0%)]
0 (0%) have returned a successful result. [0 (0%) / 0 (0%) / 0 (0%)]
189 (99%) are still in progress. [69 (36%) / 117 (62%) / 3 (2%)]
Of the tasks that have been returned successfully:
0 (0%) are pending validation. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=32192. The leading edge was at b=31768 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.33% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 17 (GFN-WR)
(As of 2016-01-07 18:20:15 UTC)
298 tasks have been sent out. [CPU/GPU/anonymous_platform: 4 (1%) / 269 (90%) / 25 (8%)]
Of those tasks that have been sent out:
27 (9%) came back with some kind of an error. [0 (0%) / 26 (9%) / 1 (0%)]
0 (0%) have returned a successful result. [0 (0%) / 0 (0%) / 0 (0%)]
271 (91%) are still in progress. [4 (1%) / 243 (82%) / 24 (8%)]
Of the tasks that have been returned successfully:
0 (0%) are pending validation. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=62148. The leading edge was at b=61558 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.96% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
We're off!
And this is strange. I'm running 3 WUs, all "18"s, on one machine:
This one's done about .5%.
This one's done about .5%.
This one's done about 2.7%!
Any idea why that one is so much faster?
Look for something non-boinc that's eating up cpu cycles.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
So last year i ran this challenge on 2 7970ghz editions, and i promised to ran on 4 gpus next year. Well i'm runnin on 4 now, pulling about 1kwt from the socket. It's a good stress test for my psu, which is enermax 1,35kwt platypus.
Well if my platypus aint gonna like it, then to hell with it, it has a valid warranty. And if it would not have a valid warranty, then... to hell with it. I will still run it, twist it, stress test it.
Good lyck to all. May the force protect you and guide you on your path (i dont mean gforce). | |
|
|
|
|
I am running cpu tasks 17mega ones on my AMD and noticed the deadline for all of them is the 11th of January, They will not get done on my computer by then. Should I abort some of them? It will take about 18 hours for each.
Thanks. | |
|
JimBHonorary cruncher
Send message
Joined: 4 Aug 11
Posts: 918
ID: 107307
Credit: 977,945,376
RAC: 0
  
|
I am running cpu tasks 17mega ones on my AMD and noticed the deadline for all of them is the 11th of January, They will not get done on my computer by then. Should I abort some of them? It will take about 18 hours for each.
Thanks.
Do not cancel them. Remember, the trickle mechanism will extend the deadline on our side. If however those tasks haven't even started by the deadline, your client will cancel them automatically.
On the other hand, if you're only running these for the challenge and wouldn't normally otherwise, feel free to cancel whichever ones you want if they wouldn't finish in time. The point I'm trying to make is that you don't have to cancel anything, it'll all work out. | |
|
nenymSend message
Joined: 23 Apr 09
Posts: 22
ID: 39029
Credit: 2,214,237,573
RAC: 958,847
        
|
We're off!
And this is strange. I'm running 3 WUs, all "18"s, on one machine:
This one's done about .5%.
This one's done about .5%.
This one's done about 2.7%!
Any idea why that one is so much faster? Have a look at stderr.txt in slots. Maybe slower tasks switched to more accurate transformations.
Example http://www.primegrid.com/result.php?resultid=677287611. Don't be surprised by times, it is ancient machine.
IMHO running GFN19 is better idea. | |
|
|
|
|
Thank you Jim. | |
|
|
|
|
Hello !
Currently running the challenge on/with 4 * GTX970.
Where can I find the app_info stated in Michael's message ? "Nvidia Maxwell GPUs may benefit from using app_info to run OCL3 instead of OCL on GFN-21 and 22."
Will the WU's run as fast as with ie a HD7950 ?
THANK YOU
Phil1966 | |
|
|
|
Hello !
Currently running the challenge on/with 4 * GTX970.
Where can I find the app_info stated in Michael's message ? "Nvidia Maxwell GPUs may benefit from using app_info to run OCL3 instead of OCL on GFN-21 and 22."
Will the WU's run as fast as with ie a HD7950 ?
THANK YOU
Phil1966
Found (almost) the answer.
Phil1966 | |
|
|
|
|
Is there a gpu choice to run the contest? Or only cpu and OCL? | |
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 938
ID: 3110
Credit: 258,708,411
RAC: 92,597
|
We're off!
And this is strange. I'm running 3 WUs, all "18"s, on one machine:
This one's done about .5%.
This one's done about .5%.
This one's done about 2.7%!
Any idea why that one is so much faster?
Turns out that one is not that much faster; it just jumped about 2% very quickly for some reason. Weird.
Hello !
Currently running the challenge on/with 4 * GTX970.
Where can I find the app_info stated in Michael's message ? "Nvidia Maxwell GPUs may benefit from using app_info to run OCL3 instead of OCL on GFN-21 and 22."
Will the WU's run as fast as with ie a HD7950 ?
THANK YOU
Phil1966
Found (almost) the answer.
Phil1966
Care to share? Especially if you have something for Linux and Nvidia?
____________
| |
|
|
|
Is there a gpu choice to run the contest? Or only cpu and OCL?
Hi Miklos, if you are asking if there are GPU work units available, yes there is. In the preferences page you should see check boxes for either Nvidia or AMD cards for each of the GFN projects. Please note, not all the GFN projects are included in this challenge. Start with 17-mega and higher.
Hope this answers your question, Rick | |
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 938
ID: 3110
Credit: 258,708,411
RAC: 92,597
|
IMHO running GFN19 is better idea.
Even on an ancient machine without AVX? On my laptop with AVX I'm running two 20's.
____________
| |
|
nenymSend message
Joined: 23 Apr 09
Posts: 22
ID: 39029
Credit: 2,214,237,573
RAC: 958,847
|
|
my non-AVX machines:
Intel C2D E6550 @ 2.33GHz: GFN19 SSE2 transformation 34 hours (2 tasks concurrently)
AMD Phenom II X6 1090T: GFN19 SSE2 transformation 46 hours (6 tasks concurrently)
AMD RM-70: GFN17mega 80bit x87 transormation 67 hours (2 tasks concurrently) - ancient machine only for fun | |
|
|
|
|
Thanks for getting back to Rick!
I have both checked in preferences, but I see only OCL options to run. Except for #22 and WR. Those are too long for my AMD computer. I was trying to run #19 tasks, but it errored out each time. | |
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 1022
ID: 301928
Credit: 543,195,386
RAC: 2
  
|
IMHO running GFN19 is better idea.
Even on an ancient machine without AVX? On my laptop with AVX I'm running two 20's.
Yes, I'm running it on some machines with either old CoreDuo either relatively modern but cheap Celeron processors. It's a best choice for these systems. Runtime is from 40 to 80 hours, depending on CPU, number of cores and memory speed (single-channel memory hurt a lot). Not much, but some scores for challenge.
Running GFN-20 on these old boxes seems to produce LESS scores per day then GFN-19 due to increased memory bandwidth requirements. GFN-20 starts to benefit a little on recent AVX CPUs with fast memory and big cache (so your laptop should be OK for it), but you must plan everything carefully and find optimal number of workunits of different sizes to fit into 8-days timeframe.
| |
|
|
|
Care to share? Especially if you have something for Linux and Nvidia?
Hello,
I only found the dedicated PrimeGrid forum, but no app_info for my config.
I will maybe switch 2*970 -> 2*HD7950 ...
Best, Phil1966 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
We are 25% of the way through this challenge. Here's the stats so far:
Challenge: Makar Sankranti
App: 25 (GFN-17-Mega)
(As of 2016-01-09 18:19:49 UTC)
21112 tasks have been sent out. [CPU/GPU/anonymous_platform: 9968 (47%) / 11053 (52%) / 91 (0%)]
Of those tasks that have been sent out:
3706 (18%) came back with some kind of an error. [1275 (6%) / 2431 (12%) / 0 (0%)]
8361 (40%) have returned a successful result. [3824 (18%) / 4508 (21%) / 29 (0%)]
9045 (43%) are still in progress. [4869 (23%) / 4114 (19%) / 62 (0%)]
Of the tasks that have been returned successfully:
3794 (45%) are pending validation. [1695 (20%) / 2090 (25%) / 9 (0%)]
4567 (55%) have been successfully validated. [2129 (25%) / 2418 (29%) / 20 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=42866672. The leading edge was at b=42809588 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.13% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 26 (GFN-18)
(As of 2016-01-09 18:19:50 UTC)
7401 tasks have been sent out. [CPU/GPU/anonymous_platform: 2527 (34%) / 4800 (65%) / 74 (1%)]
Of those tasks that have been sent out:
1549 (21%) came back with some kind of an error. [785 (11%) / 756 (10%) / 8 (0%)]
2807 (38%) have returned a successful result. [363 (5%) / 2415 (33%) / 29 (0%)]
3045 (41%) are still in progress. [1379 (19%) / 1629 (22%) / 37 (0%)]
Of the tasks that have been returned successfully:
1283 (46%) are pending validation. [137 (5%) / 1129 (40%) / 17 (1%)]
1521 (54%) have been successfully validated. [224 (8%) / 1285 (46%) / 12 (0%)]
1 (0%) were invalid. [0 (0%) / 1 (0%) / 0 (0%)]
2 (0%) are inconclusive. [2 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=1317782. The leading edge was at b=1301204 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.27% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 27 (GFN-19)
(As of 2016-01-09 18:19:50 UTC)
7136 tasks have been sent out. [CPU/GPU/anonymous_platform: 4260 (60%) / 2762 (39%) / 114 (2%)]
Of those tasks that have been sent out:
999 (14%) came back with some kind of an error. [230 (3%) / 767 (11%) / 2 (0%)]
2703 (38%) have returned a successful result. [1980 (28%) / 642 (9%) / 81 (1%)]
3434 (48%) are still in progress. [2050 (29%) / 1353 (19%) / 31 (0%)]
Of the tasks that have been returned successfully:
1178 (44%) are pending validation. [868 (32%) / 278 (10%) / 32 (1%)]
1524 (56%) have been successfully validated. [1111 (41%) / 364 (13%) / 49 (2%)]
1 (0%) were invalid. [1 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=957222. The leading edge was at b=939956 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.84% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 28 (GFN-20)
(As of 2016-01-09 18:19:50 UTC)
2247 tasks have been sent out. [CPU/GPU/anonymous_platform: 1283 (57%) / 804 (36%) / 160 (7%)]
Of those tasks that have been sent out:
519 (23%) came back with some kind of an error. [139 (6%) / 377 (17%) / 3 (0%)]
275 (12%) have returned a successful result. [112 (5%) / 138 (6%) / 25 (1%)]
1453 (65%) are still in progress. [1032 (46%) / 289 (13%) / 132 (6%)]
Of the tasks that have been returned successfully:
220 (80%) are pending validation. [87 (32%) / 115 (42%) / 18 (7%)]
53 (19%) have been successfully validated. [24 (9%) / 22 (8%) / 7 (3%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
2 (1%) are inconclusive. [1 (0%) / 1 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=731616. The leading edge was at b=727428 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.58% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 16 (GFN-21)
(As of 2016-01-09 18:19:51 UTC)
2257 tasks have been sent out. [CPU/GPU/anonymous_platform: 355 (16%) / 1842 (82%) / 60 (3%)]
Of those tasks that have been sent out:
1282 (57%) came back with some kind of an error. [140 (6%) / 1110 (49%) / 32 (1%)]
161 (7%) have returned a successful result. [0 (0%) / 156 (7%) / 5 (0%)]
814 (36%) are still in progress. [215 (10%) / 576 (26%) / 23 (1%)]
Of the tasks that have been returned successfully:
113 (70%) are pending validation. [0 (0%) / 111 (69%) / 2 (1%)]
48 (30%) have been successfully validated. [0 (0%) / 45 (28%) / 3 (2%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=34980. The leading edge was at b=31768 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 10.11% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 17 (GFN-WR)
(As of 2016-01-09 18:19:51 UTC)
945 tasks have been sent out. [CPU/GPU/anonymous_platform: 74 (8%) / 826 (87%) / 45 (5%)]
Of those tasks that have been sent out:
413 (44%) came back with some kind of an error. [11 (1%) / 393 (42%) / 9 (1%)]
1 (0%) have returned a successful result. [0 (0%) / 0 (0%) / 1 (0%)]
531 (56%) are still in progress. [63 (7%) / 433 (46%) / 35 (4%)]
Of the tasks that have been returned successfully:
1 (100%) are pending validation. [0 (0%) / 0 (0%) / 1 (100%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=62676. The leading edge was at b=61558 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.82% as much as it had prior to the challenge!
There's a WR task that's already been returned. That's impressively fast.
Also of note: GFN 19 and 20 both have more CPU tasks running than GPU tasks. That makes sense because 19 is the smallest/shortest task where AVX or FMA3 can be used.
This part doesn't make sense to me: 74 GFN-WR tasks (8% of the total) have been sent to CPUs. There's no way any CPU is coming anywhere close to completing a GFN-WR task in time to count for the challenge. Perhaps these are just random tasks being run independent of the challenge? Maybe, but not may people run GFN-WR on CPUs. In the entire database there's only 9 completed GFN-WR CPU tasks.
____________
My lucky number is 75898524288+1 | |
|
|
|
Hello,
I only found the dedicated PrimeGrid forum, but no app_info for my config.
I will maybe switch 2*970 -> 2*HD7950 ...
Best, Phil1966
Here is my app_info, based on Michael Goetz, Message 90826:
<app_info>
<app>
<name>genefer_wr</name>
<user_friendly_name>Genefer WR</user_friendly_name>
</app>
<file_info>
<name>geneferocl3_windows.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>genefer_wr</app_name>
<version_num>310</version_num>
<api_version>6.10.25</api_version>
<file_ref>
<file_name>geneferocl3_windows.exe</file_name>
<main_program/>
</file_ref>
<platform>windows_intelx86</platform>
<plan_class>OCLcudaGFNWR</plan_class>
<coproc>
<type>CUDA</type>
<count>1.000000</count>
</coproc>
<avg_ncpus>0.1</avg_ncpus>
<max_ncpus>0.1</max_ncpus>
<gpu_ram>536870912.000000</gpu_ram>
</app_version>
<app>
<name>genefer</name>
<user_friendly_name>Genefer</user_friendly_name>
</app>
<file_info>
<name>geneferocl3_windows.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>genefer</app_name>
<version_num>310</version_num>
<api_version>6.10.25</api_version>
<file_ref>
<file_name>geneferocl3_windows.exe</file_name>
<main_program/>
</file_ref>
<platform>windows_intelx86</platform>
<plan_class>OCLcudaGFN</plan_class>
<coproc>
<type>CUDA</type>
<count>1.000000</count>
</coproc>
<avg_ncpus>0.1</avg_ncpus>
<max_ncpus>0.1</max_ncpus>
<gpu_ram>536870912.000000</gpu_ram>
</app_version>
</app_info>
Works great on my two GTX970 on Windows7. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
There's a WR task that's already been returned. That's impressively fast.
It's a GTX 980 Ti running the OCL4 app (using app_info). The task completed in a little under two days.
The wingman for this task isn't that far behind. It is a very fast ATI GPU (running the standard OCL app) and it looks like it will finish in a bit under three days.
Both are incredibly impressive speeds for testing a 20 million digit number.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
Of course, my timings are based on a "single-core" tests, so they're overly optimistic. I'll need to adjust the plan on the fly. But right now, it looks like the optimal plan involves running at least one of each type of task.
And it looks like I've outsmarted myself.
I've been having some problems with the GFN GPU tasks crashing -- and there's a reasonable correlation between the errors occurring while I'm watching a video or something similar. It doesn't seem like a hardware problem so much as a driver problem, or something like that.
Not so bad if the GFN-16 gets clobbered, but a real nuisance if it's a GFN-WR, and rather painful if it's a GFN-WR that's part of the challenge. So, I tried something new: periodically manually making a copy of the genefer.ckpt file. That way, if the calculation gets corrupted and starts doing its 10-minute back-off, I can pause the task, restore the old checkpoint, and restart from an earlier time. Sounds like a plan, right?
I should know better. Trying to outsmart the BOINC system is, at best, hit and miss. There's just too many moving parts.
About 30 hours into that GFN-WR, it aborted completely. It says "computation error". The stderr text says "Instructed by the BOINC client to terminate." Oh well.
I did figure out what happened. Those extra copies of the checkpoint file? They put the task over the defined disk space limit for the task, so the BOINC client aborted the task.
I'm debating whether to try running another GFN-WR before the challenge ends. I should have just enough time, if nothing goes wrong.
____________
My lucky number is 75898524288+1 | |
|
|
|
[quote]I've been having some problems with the GFN GPU tasks crashing -- and there's a reasonable correlation between the errors occurring while I'm watching a video or something similar. It doesn't seem like a hardware problem so much as a driver problem, or something like that.
YouTube is the devil ;)
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
[quote]I've been having some problems with the GFN GPU tasks crashing -- and there's a reasonable correlation between the errors occurring while I'm watching a video or something similar. It doesn't seem like a hardware problem so much as a driver problem, or something like that.
YouTube is the devil ;)
I'm pretty sure it wasn't youtube, but rather some other type of imbedded video on one website or another.
____________
My lucky number is 75898524288+1 | |
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2639
ID: 29980
Credit: 568,393,769
RAC: 2,469
|
|
Out of interest, are you running GPU continuous, or only when computer not in use?I've found video to be too jerky when running GPU units at same time, and gaming is right out. So I'm hoping neither of those might have affected the in progress unit.
Side note: while WR gives more credits/time, there is a risk tradeoff. I went for gfn21 units instead, which is a little lower in credits/time but there is less loss if anything should go wrong. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
Out of interest, are you running GPU continuous, or only when computer not in use?I've found video to be too jerky when running GPU units at same time, and gaming is right out. So I'm hoping neither of those might have affected the in progress unit.
Continuous -- I don't see significant lag with video unless I'm running the CUDA version of genefer and have the block size set too high.
If I was going to run a game or something similar, I'd shut off BOINC crunching.
Side note: while WR gives more credits/time, there is a risk tradeoff. I went for gfn21 units instead, which is a little lower in credits/time but there is less loss if anything should go wrong.
"little" == 25% (150% vs. 120% due to the credit bonus.) The increased difficulty of running the much longer calculation is the reason for the increased credits.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Got my first WR credited, wooohooo! | |
|
|
|
Got my first WR credited, wooohooo!
It looks like you have another one coming down the pike:
http://www.primegrid.com/workunit.php?wuid=461226820
| |
|
|
|
|
You are right, about noon my time and then a couple more this afternoon. In both computers one GPU runs faster than the other one and only the faster ones will be able to do another WR before the contest is over. So I think I will switch over to #21 with the slower ones. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
We're halfway through the challenge! No GFN primes on any of the challenge ranges (yet?!?). But there's still time!
Here's the statistics after 4 days:
Challenge: Makar Sankranti
App: 25 (GFN-17-Mega)
(As of 2016-01-11 18:22:16 UTC)
32483 tasks have been sent out. [CPU/GPU/anonymous_platform: 17054 (53%) / 15317 (47%) / 112 (0%)]
Of those tasks that have been sent out:
7334 (23%) came back with some kind of an error. [2850 (9%) / 4484 (14%) / 0 (0%)]
16956 (52%) have returned a successful result. [8518 (26%) / 8379 (26%) / 59 (0%)]
8193 (25%) are still in progress. [5686 (18%) / 2454 (8%) / 53 (0%)]
Of the tasks that have been returned successfully:
4542 (27%) are pending validation. [2323 (14%) / 2189 (13%) / 30 (0%)]
12403 (73%) have been successfully validated. [6191 (37%) / 6183 (36%) / 29 (0%)]
3 (0%) were invalid. [0 (0%) / 3 (0%) / 0 (0%)]
8 (0%) are inconclusive. [4 (0%) / 4 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=42894210. The leading edge was at b=42809588 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.20% as much as it had prior to the challenge!
Normally we see about 1200 of the 17-Mega tasks completed each day. We're doing well over 3 times that much, based on the number of tasks sent out and returned. The number of tasks sent out is over 5 times the normal daily rate, taking into account the tasks that errored out. Normally I consider a challenge that runs 10 times the normal rate to be a great success, but this challenge is spread out over 6 projects. Normally a challenge concentrates everyone on a single project. This is different, so I'm very pleased with the participation.
17-Mega is somewhat unusual because, at least so far, there's more CPU tasks than GPU tasks. That's not surprising since 17-Mega is the only range in the challenge that's using the OCL2 transform on the GPUs, and that's the slowest.
App: 26 (GFN-18)
(As of 2016-01-11 18:22:17 UTC)
12389 tasks have been sent out. [CPU/GPU/anonymous_platform: 3832 (31%) / 8199 (66%) / 358 (3%)]
Of those tasks that have been sent out:
3227 (26%) came back with some kind of an error. [1314 (11%) / 1905 (15%) / 8 (0%)]
6182 (50%) have returned a successful result. [987 (8%) / 4910 (40%) / 285 (2%)]
2980 (24%) are still in progress. [1531 (12%) / 1384 (11%) / 65 (1%)]
Of the tasks that have been returned successfully:
1755 (28%) are pending validation. [216 (3%) / 1399 (23%) / 140 (2%)]
4413 (71%) have been successfully validated. [763 (12%) / 3506 (57%) / 144 (2%)]
8 (0%) were invalid. [5 (0%) / 3 (0%) / 0 (0%)]
6 (0%) are inconclusive. [3 (0%) / 2 (0%) / 1 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=1327392. The leading edge was at b=1301204 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.01% as much as it had prior to the challenge!
Normally we process about 700 GFN-18 tasks each day. We're sending out about 3 times that many each day, and so far we're getting about twice the normal rate of completed tasks.
App: 27 (GFN-19)
(As of 2016-01-11 18:22:17 UTC)
11794 tasks have been sent out. [CPU/GPU/anonymous_platform: 7608 (65%) / 3986 (34%) / 200 (2%)]
Of those tasks that have been sent out:
2014 (17%) came back with some kind of an error. [641 (5%) / 1371 (12%) / 2 (0%)]
6468 (55%) have returned a successful result. [4811 (41%) / 1491 (13%) / 166 (1%)]
3312 (28%) are still in progress. [2156 (18%) / 1124 (10%) / 32 (0%)]
Of the tasks that have been returned successfully:
1671 (26%) are pending validation. [1220 (19%) / 407 (6%) / 44 (1%)]
4791 (74%) have been successfully validated. [3589 (55%) / 1080 (17%) / 122 (2%)]
6 (0%) were invalid. [2 (0%) / 4 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=967992. The leading edge was at b=939956 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.98% as much as it had prior to the challenge!
GFN-19 is the smallest range that currently can utilize the AVX and FMA3 transforms, so you would expect it to be a popular range for CPUs -- and you would be right. Nearly two thirds of the GFN-19 tasks are being sent to CPUs.
Tasks are being sent out at around 8 times the normal daily rate, and coming back at about 5 times.
Any prime found here would be the largest GFN prime ever discovered.
Interesting trivia: My discovery of the first known n=19 GFN prime in 2011 set off a string of events that led to the current, much larger GFN search that we're running today. In 2011, it took my GTX 280 GPU about 5.5 hours to run Genefer on an n=19 number. Today I can run Genefer on a Haswell CPU core in 7.5 hours -- the CPUs are almost as fast today as the GPUs were 4 years ago.
App: 28 (GFN-20)
(As of 2016-01-11 18:22:18 UTC)
3439 tasks have been sent out. [CPU/GPU/anonymous_platform: 2011 (58%) / 1222 (36%) / 206 (6%)]
Of those tasks that have been sent out:
810 (24%) came back with some kind of an error. [273 (8%) / 534 (16%) / 3 (0%)]
1038 (30%) have returned a successful result. [627 (18%) / 344 (10%) / 67 (2%)]
1591 (46%) are still in progress. [1111 (32%) / 344 (10%) / 136 (4%)]
Of the tasks that have been returned successfully:
544 (52%) are pending validation. [306 (29%) / 203 (20%) / 35 (3%)]
491 (47%) have been successfully validated. [320 (31%) / 139 (13%) / 32 (3%)]
1 (0%) were invalid. [0 (0%) / 1 (0%) / 0 (0%)]
2 (0%) are inconclusive. [1 (0%) / 1 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=734308. The leading edge was at b=727428 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.95% as much as it had prior to the challenge!
GFN-20 hasn't been very popular since it was turned back on, averaging only about 40 tasks per day. It's therefore not much of a surprise that it's seeing a huge increase during the challenge. The bar simply isn't set very high! Tasks are going out at a rate roughly 16 times normal, and coming back at about 6 times the normal rate. These are not small tasks, and if a prime is found it would be the 10th largest known prime ever found.
App: 16 (GFN-21)
(As of 2016-01-11 18:22:18 UTC)
3440 tasks have been sent out. [CPU/GPU/anonymous_platform: 487 (14%) / 2860 (83%) / 93 (3%)]
Of those tasks that have been sent out:
1896 (55%) came back with some kind of an error. [233 (7%) / 1631 (47%) / 32 (1%)]
507 (15%) have returned a successful result. [0 (0%) / 484 (14%) / 23 (1%)]
1037 (30%) are still in progress. [254 (7%) / 745 (22%) / 38 (1%)]
Of the tasks that have been returned successfully:
305 (60%) are pending validation. [0 (0%) / 294 (58%) / 11 (2%)]
198 (39%) have been successfully validated. [0 (0%) / 186 (37%) / 12 (2%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
4 (1%) are inconclusive. [0 (0%) / 4 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=35352. The leading edge was at b=31768 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 11.28% as much as it had prior to the challenge!
GFN-21 is one of the two "low-b" ranges where b is low enough so the fastest CPU and GPU transforms can be used on all hardware. These tasks are huge. The numbers are huge. The credit is huge. The chance of finding a prime... not so much. :)
We normally do about 90 of these each day. We're currently sending out almost 400 per day, and about 125 per day have come back so far. That might not seem like much of an increase in the number of tasks being returned, but remember that these are very long tasks and even fast CPUs will need almost the entire challenge to complete one set of these.
App: 17 (GFN-WR)
(As of 2016-01-11 18:22:18 UTC)
1473 tasks have been sent out. [CPU/GPU/anonymous_platform: 130 (9%) / 1266 (86%) / 77 (5%)]
Of those tasks that have been sent out:
769 (52%) came back with some kind of an error. [81 (5%) / 668 (45%) / 20 (1%)]
145 (10%) have returned a successful result. [0 (0%) / 122 (8%) / 23 (2%)]
559 (38%) are still in progress. [49 (3%) / 476 (32%) / 34 (2%)]
Of the tasks that have been returned successfully:
99 (68%) are pending validation. [0 (0%) / 86 (59%) / 13 (9%)]
44 (30%) have been successfully validated. [0 (0%) / 34 (23%) / 10 (7%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
2 (1%) are inconclusive. [0 (0%) / 2 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=63048. The leading edge was at b=61558 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.42% as much as it had prior to the challenge!
We normally do 20 of these each day, and 145 have already been returned. About 600+ have sent out, not counting errors or tasks sent to CPUs which can't even come close to completing these tasks in 8 days. For a variety of reasons, those that can do so are preferring to run these tasks. There's a large credit bonus, so it's good for challenge points, and, of course, if a prime was found here it would be the largest known prime.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
I may have missed the answer to this somewhere.
Are points scored for completed tasks if they have not been validated by the end of the challenge? | |
|
|
|
I may have missed the answer to this somewhere.
Are points scored for completed tasks if they have not been validated by the end of the challenge?
Yes, and if there is a problem later points will be subtracted. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Somebody has a REALLY fast CPU out there...
Challenge: Makar Sankranti
App: 16 (GFN-21)
...
Of those tasks that have been sent out:
...
688 (17%) have returned a successful result. [2 (0%) / 653 (16%) / 33 (1%)]
My own Haswell at stock clocks needs about 7.5 days for an n=21. These two completed in less than 5 days. This really fast machine is a DC Haswell i7-4790K. Impressive.
(And yes, they validated. The wingmen were running GPUs which finished much earlier.)
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Feeling dumb asking this, but didn't see something answering this. Sorry if the answer will be a repeat...
For the challenge, what counts is only the tasks in the Mega...WR range that were both received and returned in the 8 day window? In other words, such a task received before the start of the challenge and returned during the challenge, and a task received during the challenge but returned after the end of the challenge don't count, right? If so, it'll suck to have bunch of 80-90% tasks by the deadline. :-)
Tuna
____________
 | |
|
|
|
In other words, such a task received before the start of the challenge and returned during the challenge, and a task received during the challenge but returned after the end of the challenge don't count, right?
Completed (and validated) tasks for each challenge are counted if they are both downloaded and returned after the challenge has begun and before it ends.
I check my system clock for accuracy against a known standard and usually wait a few extra seconds before downloading the first few tasks. If you get them before the challenge begins, even by a second, I think they will not count towards the challenge although you will still receive normal credit upon completion. | |
|
|
|
|
The countdown clock you see on the main page goes by the time of your computer. So if you computer is 5 minutes fast you will download before it starts.
Make sure your computers time is right, sink it with the world clock, or windows clock.
Yes WUs must be DL after the start and returned before it ends.
You will get credit right away for the WU. If there is a problem with the WU the points will be subtracted from your total.
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
The countdown clock you see on the main page goes by the time of your computer. So if you computer is 5 minutes fast you will download before it starts.
Make sure your computers time is right, sink it with the world clock, or windows clock.
Don't look at the countdown clock -- look above it to where it says "UTC-TIME". That shows you the actual server time. Once that shows 18:00:00 (or whatever the challenge start time is), then you know it's really the start of the challenge. You'll need to refresh the page, however. The server time display doesn't update on its own.
____________
My lucky number is 75898524288+1 | |
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 1022
ID: 301928
Credit: 543,195,386
RAC: 2
|
|
I got few GFN-19 CPU workunits which switched to x87 transform.
According to hint in another thread, I've paused and resumed these WUs; it caused Genefer to restart and they're crunching at fast transform again.
Note: this trick with manual restart via pause/unpause will work only for limited amount of time - these WU are only starting to hit maxerr at minor part of calculation (but large enough for genefer to gave up). When this "bad" part with has been processed on x87 transform, it's OK to continue in fast mode. Unfortunately, Genefer has limited number of retries, but manual kick always helps with computers :)
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Sometimes I wonder if we should stop calling these things "challenges", and simply call them by their true name:
"Prime Repellent"
Not only do we rarely actually find a prime during a challenge, but the Math Gods like to mock us. Remember the GFN challenge we ran a few years ago on 524288? Of course we didn't find any primes during the challenge -- but two (two!!!!) were found in quick succession immediately before the challenge started.
So, here we are running a GFN challenge again, this time on GFN-17-Mega through GFN-22.
GFN-17-Mega has so far done 31 thousand tasks. During the same period, GFN-17-Low, which is not part of the challenge, has done 5 thousand tasks. Which one do you think found a prime? Sure enough, it's the project that was NOT part of the challenge!
http://primes.utm.edu/primes/page.php?id=120892
Details about the new prime discovery can be found here.
We also found a mega prime during the challenge -- and, of course, it wasn't part of the challenge. It was an SR5. http://primes.utm.edu/primes/page.php?id=120887
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Are you implying that with a paradigm shift in the challenge perspective to be the sub project(s) NOT to run would result in an overall greater number of prime finds :-)
... wait ... does that lead to the extension that if I don't run any projects I win all the primes????
(says the noob as he ducks behind the couch) | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
Are you implying that with a paradigm shift in the challenge perspective to be the sub project(s) NOT to run would result in an overall greater number of prime finds :-)
... wait ... does that lead to the extension that if I don't run any projects I win all the primes????
(says the noob as he ducks behind the couch)
Perhaps the best way to find primes during a challenge is to crunch any project that's not in the challenge! (And, to boost your chances, do so when Scott Brown is away on vacation.)
Note to Charley: In 2017, maybe we should coordinate the challenge schedule so that all challenges occur while Scott is away from home.
____________
My lucky number is 75898524288+1 | |
|
|
|
Are you implying that with a paradigm shift in the challenge perspective to be the sub project(s) NOT to run would result in an overall greater number of prime finds :-)
... wait ... does that lead to the extension that if I don't run any projects I win all the primes????
(says the noob as he ducks behind the couch)
Perhaps the best way to find primes during a challenge is to crunch any project that's not in the challenge! (And, to boost your chances, do so when Scott Brown is away on vacation.)
Note to Charley: In 2017, maybe we should coordinate the challenge schedule so that all challenges occur while Scott is away from home.
Maybe we can start a kickstarter or something to try and get Scott as much away from home as possible?
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
| |
|
Scott BrownVolunteer moderator
Project administrator
Volunteer tester
Project scientist
Send message
Joined: 17 Oct 05
Posts: 2380
ID: 1178
Credit: 17,931,319,584
RAC: 10,883,776
                                            
|
|
Everybody better gear up for March 30 to April 2! (I'll be away from home at a professional conference in Washington, DC then). ;)
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
Everybody better gear up for March 30 to April 2! (I'll be away from home at a professional conference in Washington, DC then). ;)
Dang! That's too short for a special-mini GFN-WR challenge!
EDIT: But we don't seem to have a TRP-LLR challenge this year so maybe we could a a 4 day unofficial "Vacation Challenge". ;) Or possibly something more like TDP, where we only look at primes rather than tasks. Perhaps just mega-primes. Of course, the way things work, if we try to take advantage of your vacation mojo, it might guarantee that no primes will be found at all.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Perhaps the trick would be to advertise a 2-week challenge only to Mr. Brown (ppse challenge, perhaps), so that the rest of us could go on a prime-finding binge.
| |
|
|
|
|
Tell Scott Brown, March 30 to April 2 is the April's Fools' Challenge. /JeppeSN | |
|
|
|
|
With just about 11 hours to go, it's time for the usual end of challenge reminder:
At the Conclusion of the Challenge
We would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's instead of DETACHING, RESETTING, or PAUSING.
ABORTING WU's allows them to be recycled immediately; thus a much faster "clean up" to the end of a Challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
| |
|
|
|
|
Thanks for a great challenge.
I think I am in the same boat as many others. Some tasks will just miss the deadline. But it was fun. Thanks for the hard work in setting it up. | |
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 938
ID: 3110
Credit: 258,708,411
RAC: 92,597
|
|
I got all my major tasks in before the deadline. :) Though some were trickier than others. Some of the later 19's on this CPU without AVX kept shifting from SSE4 mode into SSE2 and even 80 bit mode. I found that suspending and resuming them could get them to run faster again. And it looks like they all validated, so I guess it worked.
____________
| |
|
|
|
|
Great challenge! So now the age old question, how long before all the work is validated? I'm gonna guess 2 months.
Cheers Rick
AtP - the little team that did
____________
@AggieThePew
 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
Great challenge! So now the age old question, how long before all the work is validated? I'm gonna guess 2 months.
Cheers Rick
AtP - the little team that did
My rule of thumb is 3 to 6 times the task deadline, which is 21 days for GFN 21 and 22. That would be 2 to 4 months. Normally, on long tasks I expect closer to 6x than 3x, but that wasn't the case in 2015's GFN challenge. So your 2 month estimate could turn out to be a very good guess.
____________
My lucky number is 75898524288+1 | |
|
Dave
Send message
Joined: 13 Feb 12
Posts: 3171
ID: 130544
Credit: 2,233,109,304
RAC: 574,437
    
|
|
I'll do a bit of clean-up inc WRs - got more confidence seeing these OCLs are successful.
The next excitement is OCL4 going live!
Excellent challenge, & didn't feel that long - thank you. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
The challenge is over! Here are the final statistics:
Challenge: Makar Sankranti
App: 25 (GFN-17-Mega)
(As of 2016-01-15 18:07:46 UTC)
68105 tasks have been sent out. [CPU/GPU/anonymous_platform: 42868 (63%) / 25023 (37%) / 214 (0%)]
Of those tasks that have been sent out:
18741 (28%) came back with some kind of an error. [11486 (17%) / 7252 (11%) / 3 (0%)]
38626 (57%) have returned a successful result. [22819 (34%) / 15666 (23%) / 141 (0%)]
10600 (16%) are still in progress. [8466 (12%) / 2063 (3%) / 70 (0%)]
Of the tasks that have been returned successfully:
7457 (19%) are pending validation. [4732 (12%) / 2686 (7%) / 39 (0%)]
31142 (81%) have been successfully validated. [18081 (47%) / 12959 (34%) / 102 (0%)]
9 (0%) were invalid. [1 (0%) / 8 (0%) / 0 (0%)]
18 (0%) are inconclusive. [5 (0%) / 13 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=42980418. The leading edge was at b=42809588 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.40% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 26 (GFN-18)
(As of 2016-01-15 18:07:48 UTC)
25699 tasks have been sent out. [CPU/GPU/anonymous_platform: 5242 (20%) / 18490 (72%) / 1967 (8%)]
Of those tasks that have been sent out:
6705 (26%) came back with some kind of an error. [2502 (10%) / 4153 (16%) / 50 (0%)]
14648 (57%) have returned a successful result. [2176 (8%) / 10989 (43%) / 1483 (6%)]
4291 (17%) are still in progress. [559 (2%) / 3301 (13%) / 431 (2%)]
Of the tasks that have been returned successfully:
2191 (15%) are pending validation. [125 (1%) / 1657 (11%) / 409 (3%)]
12425 (85%) have been successfully validated. [2033 (14%) / 9320 (64%) / 1072 (7%)]
26 (0%) were invalid. [16 (0%) / 9 (0%) / 1 (0%)]
6 (0%) are inconclusive. [2 (0%) / 3 (0%) / 1 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=1356636. The leading edge was at b=1301204 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 4.26% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 27 (GFN-19)
(As of 2016-01-15 18:07:49 UTC)
23666 tasks have been sent out. [CPU/GPU/anonymous_platform: 15035 (64%) / 8266 (35%) / 365 (2%)]
Of those tasks that have been sent out:
4685 (20%) came back with some kind of an error. [1562 (7%) / 3118 (13%) / 5 (0%)]
16667 (70%) have returned a successful result. [12329 (52%) / 4020 (17%) / 318 (1%)]
2269 (10%) are still in progress. [1133 (5%) / 1095 (5%) / 41 (0%)]
Of the tasks that have been returned successfully:
2210 (13%) are pending validation. [1571 (9%) / 597 (4%) / 42 (0%)]
14442 (87%) have been successfully validated. [10751 (65%) / 3415 (20%) / 276 (2%)]
13 (0%) were invalid. [5 (0%) / 8 (0%) / 0 (0%)]
2 (0%) are inconclusive. [2 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=997990. The leading edge was at b=939956 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 6.17% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 28 (GFN-20)
(As of 2016-01-15 18:07:49 UTC)
5478 tasks have been sent out. [CPU/GPU/anonymous_platform: 2600 (47%) / 2586 (47%) / 292 (5%)]
Of those tasks that have been sent out:
1966 (36%) came back with some kind of an error. [568 (10%) / 1274 (23%) / 124 (2%)]
3010 (55%) have returned a successful result. [1828 (33%) / 1027 (19%) / 155 (3%)]
501 (9%) are still in progress. [204 (4%) / 284 (5%) / 13 (0%)]
Of the tasks that have been returned successfully:
593 (20%) are pending validation. [320 (11%) / 254 (8%) / 19 (1%)]
2403 (80%) have been successfully validated. [1499 (50%) / 768 (26%) / 136 (5%)]
4 (0%) were invalid. [1 (0%) / 3 (0%) / 0 (0%)]
10 (0%) are inconclusive. [8 (0%) / 2 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=737236. The leading edge was at b=727428 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.35% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 16 (GFN-21)
(As of 2016-01-15 18:07:50 UTC)
6126 tasks have been sent out. [CPU/GPU/anonymous_platform: 595 (10%) / 5264 (86%) / 267 (4%)]
Of those tasks that have been sent out:
3358 (55%) came back with some kind of an error. [265 (4%) / 2948 (48%) / 145 (2%)]
1754 (29%) have returned a successful result. [31 (1%) / 1621 (26%) / 102 (2%)]
1009 (16%) are still in progress. [299 (5%) / 690 (11%) / 20 (0%)]
Of the tasks that have been returned successfully:
627 (36%) are pending validation. [12 (1%) / 577 (33%) / 38 (2%)]
1098 (63%) have been successfully validated. [18 (1%) / 1017 (58%) / 63 (4%)]
7 (0%) were invalid. [0 (0%) / 7 (0%) / 0 (0%)]
22 (1%) are inconclusive. [1 (0%) / 20 (1%) / 1 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=38764. The leading edge was at b=31768 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 22.02% as much as it had prior to the challenge!
Challenge: Makar Sankranti
App: 17 (GFN-WR)
(As of 2016-01-15 18:07:50 UTC)
1935 tasks have been sent out. [CPU/GPU/anonymous_platform: 154 (8%) / 1679 (87%) / 102 (5%)]
Of those tasks that have been sent out:
1107 (57%) came back with some kind of an error. [94 (5%) / 977 (50%) / 36 (2%)]
526 (27%) have returned a successful result. [0 (0%) / 462 (24%) / 64 (3%)]
302 (16%) are still in progress. [60 (3%) / 240 (12%) / 2 (0%)]
Of the tasks that have been returned successfully:
168 (32%) are pending validation. [0 (0%) / 149 (28%) / 19 (4%)]
346 (66%) have been successfully validated. [0 (0%) / 301 (57%) / 45 (9%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
12 (2%) are inconclusive. [0 (0%) / 12 (2%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=63200. The leading edge was at b=61558 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.67% as much as it had prior to the challenge!
Great work, everyone! The participation was great, and lots and lots of GFN candidates were tested. No primes were harmed (or found) during the making of this challenge.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Cleanup Status:
Jan-15: Makar Sankranti: 12731 tasks outstanding; 10535 affecting individual (277) scoring positions; 8238 affecting team (68) scoring positions.
I anticipate this cleanup will take 2 to 4 months.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
This was a good challenge, cudos to pg staff for keeping it all running so smooth, again...
I cannot believe i ended up 20-th. Cool...
Gongrats to all for their efforts, it was a good run.
What type of tasks need more attention? I'll keep my rig on it for a while.
Cheers everyone. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
What type of tasks need more attention? I'll keep my rig on it for a while.
Look on our front page. The server shows (in red) which cleanup tasks need help.
At this moment, the server is showing this:
*** 75 tasks, 25 affecting scoring positions, of Makar Sankranti Challenge (GFN-17-Mega) cleanup work are currently available! ***
*** 58 tasks, 25 affecting scoring positions, of Makar Sankranti Challenge (GFN-18) cleanup work are currently available! ***
*** 442 tasks, 354 affecting scoring positions, of Makar Sankranti Challenge (GFN-19) cleanup work are currently available! ***
*** 170 tasks, 148 affecting scoring positions, of Makar Sankranti Challenge (GFN-20) cleanup work are currently available! ***
*** 66 tasks, 62 affecting scoring positions, of Makar Sankranti Challenge (GFN-21) cleanup work are currently available! ***
*** 18 tasks, 16 affecting scoring positions, of Makar Sankranti Challenge (GFN-WR) cleanup work are currently available! ***
Note that these statistics are NOT real-time. They're updated periodically, so they may be slightly out of date.
The second number listed ("## affecting scoring positions") is the important number. That's the important cleanup tasks waiting to be sent out.
HOWEVER, to be honest, 99.9% of the cleanup time is due to waiting for abandoned tasks to timeout, and NOT waiting for cleanup tasks to be sent from the server. So feel free to help with the cleanup, or not, as you prefer. It actually doesn't make that much of a difference. Expect the cleanup task numbers to increase over the next 24-48 hours as people abort unstarted challenge tasks, but after that they'll rapidly decline as the server sends tasks as part of the normal daily processing.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Finally, before anyone asks, the reason the cleanup statistics say there's over 13,000 tasks still outstanding, but the server is saying that only a few hundred cleanup tasks need to be sent out is that the vast majority of the tasks needed to validate the remaining challenge tasks are already out being processed.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Cleanup Status:
Jan-15: Makar Sankranti: 12731 tasks outstanding; 10535 affecting individual (277) scoring positions; 8238 affecting team (68) scoring positions.
Jan-16: Makar Sankranti: 9560 tasks outstanding; 7835 affecting individual (269) scoring positions; 6131 affecting team (66) scoring positions.
Jan-17: Makar Sankranti: 7704 tasks outstanding; 6106 affecting individual (260) scoring positions; 4316 affecting team (63) scoring positions.
Jan-18: Makar Sankranti: 5909 tasks outstanding; 4639 affecting individual (248) scoring positions; 3294 affecting team (56) scoring positions.
Jan-19: Makar Sankranti: 3953 tasks outstanding; 3126 affecting individual (239) scoring positions; 2225 affecting team (55) scoring positions.
Jan-20: Makar Sankranti: 3120 tasks outstanding; 2439 affecting individual (234) scoring positions; 1297 affecting team (52) scoring positions.
Jan-21: Makar Sankranti: 2413 tasks outstanding; 1855 affecting individual (222) scoring positions; 1040 affecting team (50) scoring positions.
Jan-22: Makar Sankranti: 1958 tasks outstanding; 1466 affecting individual (206) scoring positions; 803 affecting team (43) scoring positions.
Jan-23: Makar Sankranti: 1693 tasks outstanding; 1274 affecting individual (202) scoring positions; 706 affecting team (43) scoring positions.
Jan-24: Makar Sankranti: 1491 tasks outstanding; 1093 affecting individual (192) scoring positions; 631 affecting team (42) scoring positions.
Jan-25: Makar Sankranti: 1207 tasks outstanding; 909 affecting individual (184) scoring positions; 517 affecting team (41) scoring positions.
Jan-26: Makar Sankranti: 925 tasks outstanding; 722 affecting individual (173) scoring positions; 418 affecting team (39) scoring positions.
Jan-27: Makar Sankranti: 835 tasks outstanding; 650 affecting individual (164) scoring positions; 376 affecting team (37) scoring positions.
Jan-28: Makar Sankranti: 769 tasks outstanding; 612 affecting individual (161) scoring positions; 349 affecting team (35) scoring positions.
Jan-29: Makar Sankranti: 712 tasks outstanding; 572 affecting individual (151) scoring positions; 321 affecting team (34) scoring positions.
Jan-30: Makar Sankranti: 657 tasks outstanding; 528 affecting individual (146) scoring positions; 232 affecting team (33) scoring positions.
Jan-31: Makar Sankranti: 589 tasks outstanding; 475 affecting individual (141) scoring positions; 208 affecting team (32) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Cleanup Status:
Jan-15: Makar Sankranti: 12731 tasks outstanding; 10535 affecting individual (277) scoring positions; 8238 affecting team (68) scoring positions.
Jan-31: Makar Sankranti: 589 tasks outstanding; 475 affecting individual (141) scoring positions; 208 affecting team (32) scoring positions.
Feb-1: Makar Sankranti: 526 tasks outstanding; 421 affecting individual (134) scoring positions; 188 affecting team (32) scoring positions.
Feb-2: Makar Sankranti: 457 tasks outstanding; 364 affecting individual (124) scoring positions; 167 affecting team (30) scoring positions.
Feb-3: Makar Sankranti: 422 tasks outstanding; 344 affecting individual (120) scoring positions; 151 affecting team (27) scoring positions.
Feb-4: Makar Sankranti: 395 tasks outstanding; 323 affecting individual (116) scoring positions; 146 affecting team (27) scoring positions.
Feb-5: Makar Sankranti: 354 tasks outstanding; 290 affecting individual (108) scoring positions; 124 affecting team (26) scoring positions.
Feb-6: Makar Sankranti: 318 tasks outstanding; 259 affecting individual (104) scoring positions; 110 affecting team (25) scoring positions.
Feb-7: Makar Sankranti: 284 tasks outstanding; 218 affecting individual (96) scoring positions; 92 affecting team (22) scoring positions.
Feb-8: Makar Sankranti: 260 tasks outstanding; 199 affecting individual (92) scoring positions; 84 affecting team (19) scoring positions.
Feb-9: Makar Sankranti: 239 tasks outstanding; 183 affecting individual (88) scoring positions; 78 affecting team (18) scoring positions.
Feb-10: Makar Sankranti: 211 tasks outstanding; 161 affecting individual (79) scoring positions; 68 affecting team (17) scoring positions.
Feb-11: Makar Sankranti: 188 tasks outstanding; 147 affecting individual (74) scoring positions; 61 affecting team (16) scoring positions.
Feb-12: Makar Sankranti: 171 tasks outstanding; 134 affecting individual (68) scoring positions; 57 affecting team (15) scoring positions.
Feb-13: Makar Sankranti: 156 tasks outstanding; 125 affecting individual (67) scoring positions; 48 affecting team (13) scoring positions.
Feb-14: Makar Sankranti: 145 tasks outstanding; 119 affecting individual (65) scoring positions; 46 affecting team (13) scoring positions.
Feb-15: Makar Sankranti: 138 tasks outstanding; 113 affecting individual (64) scoring positions; 42 affecting team (12) scoring positions.
Feb-16: Makar Sankranti: 127 tasks outstanding; 104 affecting individual (61) scoring positions; 38 affecting team (11) scoring positions.
Feb-17: Makar Sankranti: 116 tasks outstanding; 94 affecting individual (56) scoring positions; 35 affecting team (11) scoring positions.
Feb-18: Makar Sankranti: 109 tasks outstanding; 88 affecting individual (54) scoring positions; 35 affecting team (11) scoring positions.
Feb-19: Makar Sankranti: 102 tasks outstanding; 81 affecting individual (50) scoring positions; 35 affecting team (11) scoring positions.
Feb-20: Makar Sankranti: 99 tasks outstanding; 79 affecting individual (49) scoring positions; 34 affecting team (11) scoring positions.
Feb-21: Makar Sankranti: 88 tasks outstanding; 71 affecting individual (48) scoring positions; 17 affecting team (10) scoring positions.
Feb-22: Makar Sankranti: 82 tasks outstanding; 67 affecting individual (47) scoring positions; 15 affecting team (10) scoring positions.
Feb-23: Makar Sankranti: 80 tasks outstanding; 62 affecting individual (45) scoring positions; 15 affecting team (10) scoring positions.
Feb-24: Makar Sankranti: 76 tasks outstanding; 59 affecting individual (44) scoring positions; 15 affecting team (10) scoring positions.
Feb-25: Makar Sankranti: 70 tasks outstanding; 56 affecting individual (42) scoring positions; 15 affecting team (10) scoring positions.
Feb-26: Makar Sankranti: 65 tasks outstanding; 51 affecting individual (37) scoring positions; 14 affecting team (9) scoring positions.
Feb-27: Makar Sankranti: 59 tasks outstanding; 46 affecting individual (34) scoring positions; 12 affecting team (9) scoring positions.
Feb-28: Makar Sankranti: 56 tasks outstanding; 43 affecting individual (31) scoring positions; 8 affecting team (7) scoring positions.
Feb-29: Makar Sankranti: 51 tasks outstanding; 38 affecting individual (28) scoring positions; 6 affecting team (6) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Cleanup Status:
Jan-15: Makar Sankranti: 12731 tasks outstanding; 10535 affecting individual (277) scoring positions; 8238 affecting team (68) scoring positions.
Jan-31: Makar Sankranti: 589 tasks outstanding; 475 affecting individual (141) scoring positions; 208 affecting team (32) scoring positions.
Feb-29: Makar Sankranti: 51 tasks outstanding; 38 affecting individual (28) scoring positions; 6 affecting team (6) scoring positions.
Mar-1: Makar Sankranti: 47 tasks outstanding; 35 affecting individual (27) scoring positions; 6 affecting team (6) scoring positions.
Mar-2: Makar Sankranti: 44 tasks outstanding; 32 affecting individual (25) scoring positions; 6 affecting team (6) scoring positions.
Mar-3: Makar Sankranti: 43 tasks outstanding; 32 affecting individual (25) scoring positions; 6 affecting team (6) scoring positions.
Mar-4: Makar Sankranti: 41 tasks outstanding; 31 affecting individual (24) scoring positions; 6 affecting team (6) scoring positions.
Mar-5: Makar Sankranti: 41 tasks outstanding; 31 affecting individual (24) scoring positions; 6 affecting team (6) scoring positions.
Mar-6: Makar Sankranti: 41 tasks outstanding; 31 affecting individual (24) scoring positions; 6 affecting team (6) scoring positions.
Mar-7: Makar Sankranti: 36 tasks outstanding; 26 affecting individual (21) scoring positions; 6 affecting team (6) scoring positions.
Mar-8: Makar Sankranti: 33 tasks outstanding; 24 affecting individual (19) scoring positions; 4 affecting team (4) scoring positions.
Mar-9: Makar Sankranti: 29 tasks outstanding; 20 affecting individual (17) scoring positions; 4 affecting team (4) scoring positions.
Mar-10: Makar Sankranti: 29 tasks outstanding; 20 affecting individual (17) scoring positions; 4 affecting team (4) scoring positions.
Mar-11: Makar Sankranti: 25 tasks outstanding; 18 affecting individual (15) scoring positions; 3 affecting team (3) scoring positions.
Mar-12: Makar Sankranti: 25 tasks outstanding; 18 affecting individual (15) scoring positions; 3 affecting team (3) scoring positions.
Mar-13: Makar Sankranti: 25 tasks outstanding; 18 affecting individual (15) scoring positions; 3 affecting team (3) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Are there only n=22's left?
____________
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
Are there only n=22's left?
21 and 22.
Remember, cleanup times are almost entirely based on the deadlines, and 21 and 22 both have 21 day deadlines. As of right now there's 6 pending and 2 inconclusive 21's and 15 pending and 2 inconclusive 22's.
With the deadline extension system, there's still eight n=21 tasks and three n=22 tasks that started during the challenge that are still running. (Those aren't necessarily involved in the cleanup task scenarios, but they might be.)
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Cleanup Status:
Jan-15: Makar Sankranti: 12731 tasks outstanding; 10535 affecting individual (277) scoring positions; 8238 affecting team (68) scoring positions.
Jan-31: Makar Sankranti: 589 tasks outstanding; 475 affecting individual (141) scoring positions; 208 affecting team (32) scoring positions.
Feb-29: Makar Sankranti: 51 tasks outstanding; 38 affecting individual (28) scoring positions; 6 affecting team (6) scoring positions.
Mar-1: Makar Sankranti: 47 tasks outstanding; 35 affecting individual (27) scoring positions; 6 affecting team (6) scoring positions.
Mar-2: Makar Sankranti: 44 tasks outstanding; 32 affecting individual (25) scoring positions; 6 affecting team (6) scoring positions.
Mar-3: Makar Sankranti: 43 tasks outstanding; 32 affecting individual (25) scoring positions; 6 affecting team (6) scoring positions.
Mar-4: Makar Sankranti: 41 tasks outstanding; 31 affecting individual (24) scoring positions; 6 affecting team (6) scoring positions.
Mar-5: Makar Sankranti: 41 tasks outstanding; 31 affecting individual (24) scoring positions; 6 affecting team (6) scoring positions.
Mar-6: Makar Sankranti: 41 tasks outstanding; 31 affecting individual (24) scoring positions; 6 affecting team (6) scoring positions.
Mar-7: Makar Sankranti: 36 tasks outstanding; 26 affecting individual (21) scoring positions; 6 affecting team (6) scoring positions.
Mar-8: Makar Sankranti: 33 tasks outstanding; 24 affecting individual (19) scoring positions; 4 affecting team (4) scoring positions.
Mar-9: Makar Sankranti: 29 tasks outstanding; 20 affecting individual (17) scoring positions; 4 affecting team (4) scoring positions.
Mar-10: Makar Sankranti: 29 tasks outstanding; 20 affecting individual (17) scoring positions; 4 affecting team (4) scoring positions.
Mar-11: Makar Sankranti: 25 tasks outstanding; 18 affecting individual (15) scoring positions; 3 affecting team (3) scoring positions.
Mar-12: Makar Sankranti: 25 tasks outstanding; 18 affecting individual (15) scoring positions; 3 affecting team (3) scoring positions.
Mar-13: Makar Sankranti: 25 tasks outstanding; 18 affecting individual (15) scoring positions; 3 affecting team (3) scoring positions.
Mar-14: Makar Sankranti: 24 tasks outstanding; 17 affecting individual (14) scoring positions; 3 affecting team (3) scoring positions.
Mar-15: Makar Sankranti: 24 tasks outstanding; 17 affecting individual (14) scoring positions; 3 affecting team (3) scoring positions.
Mar-16: Makar Sankranti: 22 tasks outstanding; 16 affecting individual (13) scoring positions; 2 affecting team (2) scoring positions.
Mar-17: Makar Sankranti: 22 tasks outstanding; 16 affecting individual (13) scoring positions; 2 affecting team (2) scoring positions.
Mar-18: Makar Sankranti: 22 tasks outstanding; 16 affecting individual (13) scoring positions; 2 affecting team (2) scoring positions.
Mar-19: Makar Sankranti: 22 tasks outstanding; 16 affecting individual (13) scoring positions; 2 affecting team (2) scoring positions.
Mar-20: Makar Sankranti: 21 tasks outstanding; 15 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
Mar-21: Makar Sankranti: 21 tasks outstanding; 15 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
Mar-25: Makar Sankranti: 20 tasks outstanding; 14 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
Mar-27: Makar Sankranti: 19 tasks outstanding; 14 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
Mar-28: Makar Sankranti: 19 tasks outstanding; 14 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
Mar-29: Makar Sankranti: 19 tasks outstanding; 14 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
Mar-30: Makar Sankranti: 19 tasks outstanding; 14 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Cleanup Status:
Jan-15: Makar Sankranti: 12731 tasks outstanding; 10535 affecting individual (277) scoring positions; 8238 affecting team (68) scoring positions.
Jan-31: Makar Sankranti: 589 tasks outstanding; 475 affecting individual (141) scoring positions; 208 affecting team (32) scoring positions.
Feb-29: Makar Sankranti: 51 tasks outstanding; 38 affecting individual (28) scoring positions; 6 affecting team (6) scoring positions.
Mar-30: Makar Sankranti: 19 tasks outstanding; 14 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
Apr-1: Makar Sankranti: 18 tasks outstanding; 13 affecting individual (11) scoring positions; 1 affecting team (1) scoring positions.
Apr-2: Makar Sankranti: 17 tasks outstanding; 12 affecting individual (10) scoring positions; 0 affecting team (0) scoring positions.
Apr-3: Makar Sankranti: 17 tasks outstanding; 12 affecting individual (10) scoring positions; 0 affecting team (0) scoring positions.
Apr-4: Makar Sankranti: 13 tasks outstanding; 9 affecting individual (7) scoring positions; 0 affecting team (0) scoring positions.
Apr-6: Makar Sankranti: 13 tasks outstanding; 9 affecting individual (7) scoring positions; 0 affecting team (0) scoring positions.
Apr-6: Makar Sankranti: 10 tasks outstanding; 7 affecting individual (6) scoring positions; 0 affecting team (0) scoring positions.
Apr-7: Makar Sankranti: 8 tasks outstanding; 5 affecting individual (4) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
With 5 tasks to go, I'm going to post links to the 5 remaining workunits instead of daily updates showing the number of tasks remaining.
Note that 3 of the 5 are tasks running on a CPU -- and currently progressing too slowly to finish within the maximum 84 day deadline. So they'll likely chew up 84 days and then be resent to new computers. Two of those three tasks are running on the same computer. (We intentionally don't assume that these tasks can't complete in time and preemptively cancel the tasks because it's possible that the computer might speed up.)
Several such tasks have just exceeded that 84 day limit and got recycled -- that's why the number of tasks we're waiting for has dropped in the last couple of days.
I'm rethinking the wisdom of allowing CPU tasks on n=22.
Anyway, here's the 5 work units remaining.
We need at least one of these two to complete:
http://www.primegrid.com/workunit.php?wuid=461136495
http://www.primegrid.com/workunit.php?wuid=461228310
We also need all three of these tasks to complete:
http://www.primegrid.com/workunit.php?wuid=461227586
http://www.primegrid.com/workunit.php?wuid=461227390
http://www.primegrid.com/workunit.php?wuid=461609482
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Four to go:
We need at least one of these two to complete:
http://www.primegrid.com/workunit.php?wuid=461136495
http://www.primegrid.com/workunit.php?wuid=461228310
We also need both of these tasks to complete:
http://www.primegrid.com/workunit.php?wuid=461227586
http://www.primegrid.com/workunit.php?wuid=461609482
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
Three to go:
http://www.primegrid.com/workunit.php?wuid=461136495
http://www.primegrid.com/workunit.php?wuid=461227586
http://www.primegrid.com/workunit.php?wuid=461609482
Judging by these tasks' progress so far:
* The first two tasks currently have wingmen that are running so slowly that they will not finish (or even be close to finishing) when the task hits the 84 day extended deadline. That will happen for both tasks on April 27th. New tasks will be sent out at that time.
* We're in better shape with the third task. This task will time out on April 29th, but the task is currently 74% done and at the current pace will complete somewhere between April 26th and May 12th. Even if it is marked late and a new task is sent out to replace it, when this task finishes it will count. So I expect this task to be finished no later than May 12th.
EDIT: We've increased the number of tasks for those first two work units to 3 so that we don't have to wait until the 27th for them to time out.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
One of the three has completed, so there's now just two remaining:
http://www.primegrid.com/workunit.php?wuid=461227586
http://www.primegrid.com/workunit.php?wuid=461609482
We tweaked the first work unit to send out an extra task, which it did a week ago. That computer hasn't started crunching the task yet, however, so we'll keep waiting. It will time out in about two weeks unless it starts doing something.
The second work unit's task is likely to finish in a week, but it's going to time out before then, so it's possible a replacement task would be sent to a fast computer and finish before then. The almost-finished result will still count even after it times out.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
|
One of the two remaining tasks has completed, so there's now just one remaining:
http://www.primegrid.com/workunit.php?wuid=461227586
We tweaked the remaining work unit to send out an extra task because the then-running task was progressing much too slowly to finish before it times out. Since then, that task has indeed timed out, and the server has sent out a third task, so there's actually 2 running at this moment. In theory, anyway. Neither of the two "in progress" tasks appears to actually be working on this task yet.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
The remaining result has been validated :)
____________
DeleteNull | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,586,193
RAC: 178,879
|
The remaining result has been validated :)
Awesome. Time to go flip some switches.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
With the final unit validated, we can announce the winners!
The top 3 participants are:
1. Ross*
2. zunewantan
3. Van Zimmerman
The top 3 teams are:
1. Sicituradastra.
2. Aggie The Pew
3. SETI. Germany
The overall stats have also been updated.
Thanks for participating and see you at the next challenge, 20-25 June on PPS Mega.
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
| |
|
Message boards :
Number crunching :
Makar Sankranti Challenge |
