Welcome to the Geek Pride Day Challenge
The third challenge of the 2022 Series will be a 5-day challenge celebrating geeks, freaks, nerds, dorks, dweebs, and "weird" people of all kinds! The challenge will be offered on the GFN-19 subproject, beginning 25 May 18:00 UTC and ending 30 May 18:00 UTC.
May 25: ¡Feliz día del orgullo friki!
Geek Pride Day originated in 2006, when Spanish internet personality Señor Buebo created the Del Día Del Orgullo Friki website. It was originally a celebration of enthusiasts of traditionally-geeky franchises like Star Wars, Marvel Comics and so on. Today, though, when terms like "nerd" and "freak" are still sometimes used as insults, it's important to have a day to remember who we really are: people who are passionate about something! Whatever you love to geek out about, whether it's Minecraft, black holes, or prime numbers, you are part of one of the coolest, biggest, and weirdest communities in the universe!
To participate in the Challenge, please select only the GFN-19 subproject in your PrimeGrid preferences section.
Note: The deadline for some of these WUs is longer than five days, so make sure your computer is able to return the WUs within the challenge time-frame. Only tasks issued AFTER the start time and returned BEFORE the finish time will be counted.
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.
- Windows: Nvidia GPU (OpenCL): 32 bit, AMD/ATI GPU (OpenCL): 32 bit, CPU: 64 bit, 32 bit
- Linux: Nvidia GPU (OpenCL): 32 bit, 64 bit, AMD/ATI GPU (OpenCL): 32 bit, 64 bit, CPU: 64 bit, 32 bit
- Mac: Nvidia GPU (OpenCL): 64 bit, AMD/ATI GPU (OpenCL): 64 bit, CPU: 64 bit, 32 bit
A Cautionary Reminder
ATTENTION: The primality programs Genefer (for CPUs) and GeneferOCL (for GPUs) 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.
GFN-19 WU's are currently averaging 40 hours on CPU (on one core) and 2 hours on GPU.
For a general idea of how your GPU stacks up, you can have a look at the fastest GPUs list.
If your CPU is highly overclocked, please consider "stress testing" it. Overclocking your GPU is not recommended at all for GeneferOCL. 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.
Scores will be kept for individuals and teams. Only work units issued AFTER May 25th 18:00 UTC and received BEFORE May 30th 18:00 UTC will be considered for credit.
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. :)
More information on Generalized Fermat Numbers and the Genefer program
Best of Luck to everyone!
Time flies like an arrow. Fruit flies like a banana.
Here is some information on multi-threading.
The allocated data size is 10 MB.
On processors with two memory channels, the throughput is generally optimal if the data size of all tasks is lower than the L3 cache size. For example, i7-11700K: L3 = 16 MB => 1 task; i7-12700K: L3 = 25 MB => 1 or 2 tasks; Ryzen 5950X: L3 = 2 x 32 MB => 6 tasks or less.
If the L3 cache size is below 10 MB, hyper-threading may increase the speed of genefer because two threads per core hide the memory latency.
Processors with four memory channels can be more efficient if the data size is greater than the L3 cache size.
On Ryzen processors with two CCX, it is recommanded that the affinity of genefer threads is set (see http://www.primegrid.com/forum_thread.php?id=9905).