log in |
Message boards : Number crunching : Trial Factoring
Previous · 1 . . . 17 · 18 · 19 · 20 · 21 · 22 · 23 · Next
Author | Message |
---|---|
Does it work yet, running one task per GPU, with multiple GPUs on Windows? Back in April, I think it was still being worked on. But I haven't heard any update since then. Got it. I will stay tuned for more info. ____________ Reno, NV Team: SETI.USA | |
ID: 6679 · Rating: 0 · rate: / Reply Quote | |
cuda11/11.1 linux apps are up, could still need some tweaking. If you have a RTX3080/90 pls test if you are getting work depends on driver and cuda version, thx to DeleteNull to made it possible! | |
ID: 6951 · Rating: 0 · rate: / Reply Quote | |
After some tweaking the plan_class_spec is working now correctly. | |
ID: 6958 · Rating: 0 · rate: / Reply Quote | |
./mfaktc.exe: error while loading shared libraries: libcudart.so.10.1: cannot open shared object file: No such file or directory (for 2xxx cards) | |
ID: 6976 · Rating: 0 · rate: / Reply Quote | |
Boy, points sure went to shit the past day or 2. | |
ID: 7106 · Rating: 0 · rate: / Reply Quote | |
Boy, points sure went to shit the past day or 2. Something odd in the points awarding is happening. See my message: http://srbase.my-firewall.org/sr5/forum_thread.php?id=1498&postid=7130#7130 | |
ID: 7131 · Rating: 0 · rate: / Reply Quote | |
Boy, points sure went to shit the past day or 2. UPDATE: I was seeing a WU results delay and likely not related to your concern. | |
ID: 7152 · Rating: 0 · rate: / Reply Quote | |
./mfaktc.exe: error while loading shared libraries: libcudart.so.10.1: cannot open shared object file: No such file or directory (for 2xxx cards) Hi, I get these errors. Where i can find libcudart.so.10.1? Linux Mint 19.3 Thanx for hints | |
ID: 7391 · Rating: 0 · rate: / Reply Quote | |
./mfaktc.exe: error while loading shared libraries: libcudart.so.10.1: cannot open shared object file: No such file or directory (for 2xxx cards) see FAQ | |
ID: 7392 · Rating: 0 · rate: / Reply Quote | |
This has probably been answered before but i hate boinc forum search, is it possible to select a particular cuda app version? You said earlier that planclass is working i think, can that be used to specify i want cuda100 only? | |
ID: 7522 · Rating: 0 · rate: / Reply Quote | |
This has probably been answered before but i hate boinc forum search, is it possible to select a particular cuda app version? You said earlier that planclass is working i think, can that be used to specify i want cuda100 only? If you are under these specs then yes but cant specified by yourself: <min_cuda_version>11000</min_cuda_version>
<min_driver_version>45036</min_driver_version> | |
ID: 7523 · Rating: 0 · rate: / Reply Quote | |
New linux cuda100 TF app is up which included the libcudart.so.10.1 in the zip. I hope this fixes the linking issue (only affecting users which have cuda11 installed) | |
ID: 7528 · Rating: 0 · rate: / Reply Quote | |
Got 1 time the cuda 100 TF Workunits and all other times the non working 0.12 Cuda 111 Workunits. Is there an option for selecting the cuda 100 Version? | |
ID: 7640 · Rating: 0 · rate: / Reply Quote | |
Got 1 time the cuda 100 TF Workunits and all other times the non working 0.12 Cuda 111 Workunits. Is there an option for selecting the cuda 100 Version? no, its defined in the plan_class | |
ID: 7641 · Rating: 0 · rate: / Reply Quote | |
<core_client_version>7.9.3</core_client_version> | |
ID: 7642 · Rating: 0 · rate: / Reply Quote | |
It must be possible to install only a newer glibc version | |
ID: 7643 · Rating: 0 · rate: / Reply Quote | |
The range 72-73bit is nearly done. The rest of the work was uploaded on the server. | |
ID: 7691 · Rating: 0 · rate: / Reply Quote | |
The range 72-73bit is nearly done. The rest of the work was uploaded on the server. So does that mean that we move onto the 73-74 bit range next? If so, does that have a large effect on TF as a project? | |
ID: 7699 · Rating: 0 · rate: / Reply Quote | |
So does that mean that we move onto the 73-74 bit range next? If so, does that have a large effect on TF as a project? The impact of trial factoring from 73 bit to 74 bit, will mean following: Tasks to factor: 16,865,230 Likeliness of factor: 1.435 percent (maybe little higher) First time tests saved by factoring: 242,016 tests. The impact is as you can see very high. A 12 core 2.3 GHz Xeon (not modern at all) uses about 48 CPU days per test at n=100M. It then uses 192 days at n=200M. It then uses 768 days at n=400M. It then uses 3,072 days at n=800M. From n=100M to n=200M tests saved 16,232 (1,947,840 CPU days saved) From n=200M to n=400M tests saved 51,851 (24,888,480 CPU days saved) From n=400M to n=800M tests saved 116,577 (223,827,840 CPU days saved) So the impact is a whooping 250,664,160 saved CPU days of testing, on a 12 core 2.3 GHz Xeon and by all means very huge and meaningfull. Thanks for asking the question :) Take care. | |
ID: 7700 · Rating: 0 · rate: / Reply Quote | |
Thank you, that’s fascinating! | |
ID: 7703 · Rating: 0 · rate: / Reply Quote | |
Message boards :
Number crunching :
Trial Factoring