Asteroids@home: New CUDA102 application was released
Running a pair of test WUs now, on a GTX 1070 under Windows. Estimated 33min until completion. Looks like Asteroids is STILL a CPU project (Ryzen 3000 series runs a CPU task in under an hour on average). First one finished in 26m19s.Today we released a new CUDA102 application v102.14 for both Windows & Linux.
A bug was fixed where application causes 100% utilisation of whole CPU core (thread in hyperthreaded CPUs)
https://boinc.bakerlab.org/rosetta/. They made this change because companies, who want to contribute computer time, asked for it.
stream said:First step of integration includes partial replacement of current LLR by LLR2 in "Gerbicz runtime error check" mode for some projects and platforms:
Remaining platforms and projects will continue to use old LLR (residues are compatible).
- Platforms: Windows-64 and Linux-64 only;
- Projects: all except base-2 "-1" tests, because LLR2 uses another testing method and incompatible residues.
Please note that it will not enable fast validation scheme yet. Only Gerbicz runtime error check will be enabled. It will allow to catch all types of hardware and, what is most important, software errors. Ideally, we should not see mismatching residues anymore. Even completely broken/overheating computer should be either eventually complete the test, even abort it after few attempts, but never return wrong residue.
(found via a post from pschoefer in the SETI.Germany forum)Pavel Atnashev said:The importance of Gerbicz check is that it is very good at detecting local hardware and software errors almost for free, and provides the way to recover from them. We should see a dramatic drop in invalid results. That's why it's important to start using it asap.
Update:pschoefer said:In the long run, double checking will be revolutionized by this. More on this in due course.
The tasks I'm getting are only 5 - 7 MB each...
Two weeks ago, RakeSearch rebooted with an application "SAT-based search for orthogonal pairs of DLS of order 10":RakeSearch is about to end soon:
The last batch of WUs were sent to hosts a few days ago. The site will stay online, but no new tasks will be generated anymore. The findings of the project are public.
a while back, my 7742 had 20 some tasks waiting on memory, and that box has 128 gig. But with 124 threads of Rosetta, thats only one gig per task. I have one box right now (my other 7742) with one task waiting on memory.
I can't figure out how to make screen copies in linux, but this is the thrird 40 gig process that I have seen. My 7452 has 128 gig of ram, and most processes in Rosetta are taking 1.5 to 2 gig ram (60 Rosetta tasks or so) but now I have 20 tasks waitng for memory and that 40 gig one.
Sounds like after the WCG challenge, I may have a new project ! Thanks !
Thanks! I'll put my Linux VM(s) to work after the QuChemPedIA sprint ends.
So I let my computer run the project for a little while just to see the results, and it appears that the reason for the "insane" points is because the points algorithm is not written properly. It is rewarding credits equal to the Run time (seconds) column instead of the calculated Credit column.Linux only. CPU only. Points are insane.
|Thread starter||Similar threads||Forum||Replies||Date|
|Security certificate problems on multiple projects||Distributed Computing||5|
|Which projects create the most heat? And are PCIe bandwidth limited?||Distributed Computing||17|
|Zen 3 processors with 3x the L3 cache: Impact on DC projects||Distributed Computing||2|
|E||WCG MIP project ending||Distributed Computing||2|
|S||1 million point project challenge||Distributed Computing||49|