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

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise
1) Message boards : Number crunching : √Čvariste Galois's Birthday Challenge (Message 144551)
Posted 208 days ago by niktak11
Do you just allow them to run on only even cores?
2) Message boards : Number crunching : √Čvariste Galois's Birthday Challenge (Message 144543)
Posted 208 days ago by niktak11
it seems like just using the Prim95 benchmark isn't sufficient? Do the results deviate from real world applications?

It is a starting point, and there can be differences.

For example, I just did a fresh install on a 3700X system. I know it should be best with 1 task per core (although I have seen elsewhere that using SMT might improve it further, I haven't tested this). When I set it up with 1 task per core, I saw Windows being stupid, putting two tasks on the 1st core, with the last core idle. I had to manually set affinity to correct this.

From experience, Windows needs a nudge at times when running 1 thread per task on HT/SMT enabled CPUs. Something changes when running more than one thread per task and that requires less manual intervention.

With my 3900x, it seems that I get higher throughput with this project by running 3 cores/task (4 at once) than a single task per core (12 at once).
3) Message boards : Number crunching : Alan Turing's Birthday Challenge (Message 141026)
Posted 328 days ago by niktak11
I can't seem to get multiple tasks per GPU working. I have this in my app_config.xml file. Everything else in that file is working fine.

<app>
<name>pps_sr2sieve</name>
</app>
<app_version>
<app_name>pps_sr2sieve</app_name>
<plan_class>cudaPPSsieve</plan_class>
<avg_ncpus>0.1</avg_ncpus>
<ngpus>0.5</ngpus>
</app_version>


try this:

<app_config>
<app>
<name>pps_sr2sieve</name>
<max_concurrent>2</max_concurrent>
</app>
<app_version>
<app_name>pps_sr2sieve</app_name>
<plan_class>cudaPPSsieve</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<ngpus>.5</ngpus>
</app_version>
</app_config>

It turns out Windows changed my existing app_config.xml file to app_config.xml.txt lol
4) Message boards : Number crunching : Alan Turing's Birthday Challenge (Message 140997)
Posted 328 days ago by niktak11
I can't seem to get multiple tasks per GPU working. I have this in my app_config.xml file. Everything else in that file is working fine.

<app>
<name>pps_sr2sieve</name>
</app>
<app_version>
<app_name>pps_sr2sieve</app_name>
<plan_class>cudaPPSsieve</plan_class>
<avg_ncpus>0.1</avg_ncpus>
<ngpus>0.5</ngpus>
</app_version>
5) Message boards : Number crunching : Tour de Primes 2020 (Message 137734)
Posted 461 days ago by niktak11
I finally found a mega prime
6) Message boards : Generalized Fermat Prime Search : GFN-16 MEGA Prime Search starts March, 14, 2019 (Message 136979)
Posted 472 days ago by niktak11
[...]If this follows other LLR work, I'd expect optimal running configuration to be 2 cores per task for pretty much all recent CPUs.[...]

I turned off HT on my 3970X, so it's running 36 threads on 36 cores. Then I ran an experiment, running just a single task:

8 cores: 1:41
4 cores: 1:29
2 cores: 1:55

Those time are really good, and it seems that 2 cores is the best choice on this machine for maximum work. But, once I cranked up the number of tasks to use all the cores, 2 per task, times dropped back to the 4-6 hour range. Not really sure why this would be, considering it has 128mb of L3?



I noticed the same thing happening to me with my 3900x. Running 1 task with 3 threads is much faster than running 4 tasks with 3 threads each. I'm guessing windows isn't smart enough to keep each task confined to a single CCX and it's wasting a lot of time getting data from cache in other CCXs. The core clock is not much different for me in either scenario.
7) Message boards : AP26 - AP27 Search : AP27 FOUND!!! (Message 133219)
Posted 600 days ago by niktak11
Time to start looking for an AP28
8) Message boards : Generalized Fermat Prime Search : GFN21 GFN22 Scoreboard, post your times/hardware (Message 124829)
Posted 854 days ago by niktak11
Some AMD numbers...

RX480
GFN 21: 85,636.77 sec
GFN 22: 328,450.69 sec

Vega 64 LC
GFN 21: 38,716.65 sec
GFN 22: 157,553.05 sec

Waiting for Radeon VII...

Looks like the rumor that the VII would have an uncapped FP64 was incorrect. RIP...
9) Message boards : Generalized Fermat Prime Search : GFN21 GFN22 Scoreboard, post your times/hardware (Message 124748)
Posted 856 days ago by niktak11
The upcoming Radeon VII should be beastly at GFN21 and GFN22. Nearly 7tflops of FP64 for $699. Might be able to beat a Titan V since it has over 50% more memory bandwidth.
10) Message boards : Number crunching : Winter Solstice Challenge (Message 123394)
Posted 888 days ago by niktak11
If you don't have an RTX 20x0 card (the new ones), 399 is still the last suitable driver.

Thanks. That dropped my estimated runtime on a 1080 from 11 hours to 6 hours.


Next 10 posts
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2021 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 3.43, 3.57, 3.77
Generated 18 May 2021 | 4:42:01 UTC