Posts by rebirther
log in
1) Message boards : Number crunching : Results of bases (Message 10065)
Posted 21 hours ago by Profile rebirther
R867 tested to n=600k (500-600k)

nothing found, 1 remain
2) Message boards : Number crunching : Results of bases (Message 10064)
Posted 1 day ago by Profile rebirther
S816 tested to n=600k (500-600k)

nothing found, 1 remain
3) Message boards : Number crunching : Results of bases (Message 10063)
Posted 1 day ago by Profile rebirther
R275 tested to n=1M (600k-1M)

nothing found, 1 remain
4) Message boards : Number crunching : Bases loaded (Message 10062)
Posted 1 day ago by Profile rebirther
S513
- n=50-100k
- runtime 2min24s-10min48s (AVX@3.8Ghz)
- 50-80k = 20 credits
- 80-100k = 40 credits
- Sierpinski / Riesel Base - short
- deadline 3 days
5) Message boards : Science : base S513 (running) (348k) (Message 10061)
Posted 1 day ago by Profile rebirther
- n=50-100k, 348k left
- runtime 2min24s-10min48s (AVX@3.8Ghz)
- 688851 WUs
6) Message boards : Number crunching : Bases loaded (Message 10060)
Posted 1 day ago by Profile rebirther
S25
- n=350-600k
- runtime 22min-1h39min (AVX@3.8Ghz)
- 350-400k = 80 credits
- 400-500k = 180 credits
- 500-600k = 300 credits
- Sierpinski Base
- deadline 3 days
- TOP5000 primes
7) Message boards : Science : base S25 (running) (80k) (Message 10059)
Posted 1 day ago by Profile rebirther
- n=350-600k, 80k left
- runtime 22min-1h18min (AVX@3.8Ghz)
- 250623 WUs
8) Message boards : Number crunching : Bases loaded (Message 10058)
Posted 2 days ago by Profile rebirther
R25
- n=300-600k
- runtime 10min51s-1h39min (AVX@3.8Ghz)
- 300-400k = 80 credits
- 400-500k = 120 credits
- 500-550k = 240 credits
- 550-600k = 300 credits
- Sierpinski / Riesel Base
- deadline 3 days
- TOP5000 primes
9) Message boards : Science : base R16 (preparing) (15k) (Message 10056)
Posted 4 days ago by Profile rebirther
- n=1-1.5M, 15k left (443, 2297, 9519, 13380, 13703, 19464, 19772, 21555, 23669, 24987, 26378, 28967, 29885, 31859, 33023)
- runtime ? (AVX@3.8Ghz)
- 46715 WUs
10) Message boards : Number crunching : Bases loaded (Message 10055)
Posted 4 days ago by Profile rebirther
R45
- n=500-700k
- runtime 1h25min-2h13min (AVX@3.8Ghz)
- 500-600k = 350 credits
- 600-650k = 450 credits
- 650-700k = 500 credits
- Sierpinski / Riesel Base - average2
- deadline 3 days
11) Message boards : Number crunching : Results of bases (Message 10054)
Posted 4 days ago by Profile rebirther
S784 tested to n=600k (400-600k)

nothing found, 1 remain
12) Message boards : Number crunching : Results of bases (Message 10053)
Posted 5 days ago by Profile rebirther
R82 tested to n=300k (100-300k)

15 primes found, 51 remain

16131*82^101531-1 found by [SG-FC] dingdong
8499*82^104320-1 found by XAVER
1991*82^104842-1 found by Science United
13779*82^126143-1 found by [SG-FC] dingdong
290*82^126063-1 found by Science United
2543*82^140448-1 found by [SG-FC] dingdong
4083*82^140914-1 found by Science United
2157*82^165344-1 found by Doug
2588*82^179422-1 found by gemini8
8384*82^198853-1 found by Science United
14531*82^210023-1 found by [SG-FC] dingdong
21282*82^252052-1 found by grcpool.com
12791*82^269743-1 found by Science United
16767*82^274977-1 found by Arkhenia
14687*82^283829-1 found by Science United
13) Message boards : Number crunching : Bases loaded (Message 10052)
Posted 6 days ago by Profile rebirther
S457
- n=50-100k
- runtime 2min-10min37s (AVX@3.8Ghz)
- 50-80k = 20 credits
- 80-100k = 40 credits
- Sierpinski Base - short
- deadline 3 days
14) Message boards : Science : base S457 (running) (326k) (Message 10051)
Posted 6 days ago by Profile rebirther
- n=50-100k, 326k left
- runtime 2min-10min37s (AVX@3.8Ghz)
- 658724 WUs
15) Message boards : News : Testing new apps started (Message 10043)
Posted 11 days ago by Profile rebirther
new cuda120 v39 TF mfaktc linux app is up

changelog:
- recompiled fix for sm_70
16) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 10040)
Posted 11 days ago by Profile rebirther
v39 with cc7 is up for linux
17) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 10038)
Posted 11 days ago by Profile rebirther


Yes, this was only testing the current plan_class with Cuda111 while there are some different things in config. It looks like the app was not compiled with cc7 but cc6. For cc10 we will have a separate app of course.


your current cuda120 app seems to support 5.0 (maybe, dont have any to test), 6.0, 6.1, 7.5, 8.6, 8.9, neglecting 7.0.

it seems clear that the project is only looking at the driver version or embedded cuda version for deciding which app to send. using an app_config WILL NOT WORK.


could you recompile the cuda120 app to include ALL CCs and add in 7.0?


Need to ask, windows and linux can be different.


I'm talking about the Linux cuda120 app


yes, compiling is in progress.
18) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 10035)
Posted 11 days ago by Profile rebirther


Yes, this was only testing the current plan_class with Cuda111 while there are some different things in config. It looks like the app was not compiled with cc7 but cc6. For cc10 we will have a separate app of course.


your current cuda120 app seems to support 5.0 (maybe, dont have any to test), 6.0, 6.1, 7.5, 8.6, 8.9, neglecting 7.0.

it seems clear that the project is only looking at the driver version or embedded cuda version for deciding which app to send. using an app_config WILL NOT WORK.


could you recompile the cuda120 app to include ALL CCs and add in 7.0?


Need to ask, windows and linux can be different.
19) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 10033)
Posted 11 days ago by Profile rebirther
all cuda120 tasks error out on my V100s. in the same way that crash's P100s were erroring.

did you omit support for CC 7.0 (titan V and V100 at this CC level)? as i pointed out before you need to explicitly add support for every CC level individually.


We can try to use cuda100 WUs with an app_config. Thats the oldest app which we are running.

<app_config> <app_version> <app_name>TF</app_name> <plan_class>cuda100</plan_class> <min_gpu_ram_mb>384</min_gpu_ram_mb> <gpu_ram_used_mb>384</gpu_ram_used_mb> <gpu_peak_flops_scale>0.22</gpu_peak_flops_scale> <cpu_frac>0.01</cpu_frac> </app_version> </app_config>


tried it. didnt work. this app config does not work. it will not limit the project to only getting the cuda100 app.

same results on a Titan V (same cc-7.0), instant error.

I'm guessing the problem is how the app was compiled without cc 7.0 support.


We can only try this

<app_config> <app_version> <app_name>TF</app_name> <plan_class>cuda111</plan_class> <min_gpu_ram_mb>384</min_gpu_ram_mb> <gpu_ram_used_mb>384</gpu_ram_used_mb> <gpu_peak_flops_scale>0.22</gpu_peak_flops_scale> <cpu_frac>0.01</cpu_frac> </app_version> </app_config>


Or the app was not compiled with cc7, P100 was working, right?


this method of using an app_config to try to force what app gets sent, do not work. i've never had this work reliably and it didnt work for crashtech when you suggested it last time. an app config is designed to enact some configuration on apps that are already downloaded. it does not impose any influence on what the project server actually sends me.

i think your app was not compiled with CC 7.0 support. and if you didn't do it on the latest app, I would guess you didnt do it on the older apps either.

P100 works as far as I know. but that's because you fixed it by recompiling the app to include the CC 6.0 support.

when compiling cuda apps you cannot just put a minimum value. you need to put ALL values that you want to support. to support everything from CC5.0+ you need to explicitly state every version (5.0, 5.2, 6.0, 6.1, 7.0, 7.5, 8.6, 8.9)

5.0 - GM100 Maxwell
5.2 - GM200 Maxwell
6.0 - GP100 Pascal
6.1 - GP102+ Pascal
7.0 - GV100 Volta (Titan V and V100)
7.5 - TU102+ Turing
8.0 - GA100 Ampere
8.6 - GA102+ Ampere
8.9 - AD102+ Ada Lovelace
9.0 - GH100 Hopper

and you're going to have to recompile again in the future to add 10.x something if you want to support the upcoming Blackwell GPUs.


Yes, this was only testing the current plan_class with Cuda111 while there are some different things in config. It looks like the app was not compiled with cc7 but cc6. For cc10 we will have a separate app of course.
20) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 10031)
Posted 11 days ago by Profile rebirther
all cuda120 tasks error out on my V100s. in the same way that crash's P100s were erroring.

did you omit support for CC 7.0 (titan V and V100 at this CC level)? as i pointed out before you need to explicitly add support for every CC level individually.


We can try to use cuda100 WUs with an app_config. Thats the oldest app which we are running.

<app_config> <app_version> <app_name>TF</app_name> <plan_class>cuda100</plan_class> <min_gpu_ram_mb>384</min_gpu_ram_mb> <gpu_ram_used_mb>384</gpu_ram_used_mb> <gpu_peak_flops_scale>0.22</gpu_peak_flops_scale> <cpu_frac>0.01</cpu_frac> </app_version> </app_config>


tried it. didnt work. this app config does not work. it will not limit the project to only getting the cuda100 app.

same results on a Titan V (same cc-7.0), instant error.

I'm guessing the problem is how the app was compiled without cc 7.0 support.


We can only try this

<app_config> <app_version> <app_name>TF</app_name> <plan_class>cuda111</plan_class> <min_gpu_ram_mb>384</min_gpu_ram_mb> <gpu_ram_used_mb>384</gpu_ram_used_mb> <gpu_peak_flops_scale>0.22</gpu_peak_flops_scale> <cpu_frac>0.01</cpu_frac> </app_version> </app_config>


Or the app was not compiled with cc7, P100 was working, right?


Next 20

Main page · Your account · Message boards


Copyright © 2014-2024 BOINC Confederation / rebirther