| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 52
|
|
| Author |
|
|
pramo
Veteran Cruncher USA Joined: Dec 14, 2005 Post Count: 716 Status: Offline Project Badges:
|
Waiting to build new rig until kepler.and ivy bridge are released. Can't wait..... Keep up the great.work guys!!! I said the same thing about Sandy Bridge. Kind of glad I waited with the GPU stuff happening. Can't wait myself even though it'll be as a "slower adopter" ![]() ![]() |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
Will the beta be announced with an opt in option from our preferences or will GPUs be detected and the betas run on there own? There will be an option on the My Projects page and near the project selection on the device profiles that you will have to check in order to receive work for GPU. This option will be added as part of the updates tomorrow so you will be able to select it ahead of the start of the beta testing for gpu. You will have to also be signed up to be a beta tester on order to participate in beta testing. |
||
|
|
X-Files 27
Senior Cruncher Canada Joined: May 21, 2007 Post Count: 391 Status: Offline Project Badges:
|
Has the minimum gpu requirements has been drawn or still in the works?
----------------------------------------![]() ![]() |
||
|
|
johncmacalister2010@gmail.com
Veteran Cruncher Canada Joined: Nov 16, 2010 Post Count: 799 Status: Offline Project Badges:
|
The upgrade on Tuesday is being done so that we can run GPU applications. The new server software that we will use is up to date with recent code from Berkeley. The older code that we have currently running doesn't have what is needed to send out application versions for GPUs. Therefore, we are updating and will be using updated server software. However, this update will have some disruptions when we deploy it. One of the biggest disruptions will be the new way that the server code handles identifying 'trusted' computers (ones that can process non-redundant computations without a wingman) and 'reliable' computers (ones that process resent workunits quickly). The determination of 'trusted' and 'reliable' will be changed from being determined for a specific device to being determined for a specific pairing of a device and version of a research application. This means that your computer could be trusted on FightAIDS@Home but perhaps not on Computing for Clean Water (for example). Since initially we will not have data at the device-application version level, no-one will be trusted or reliable until the data is accumulated to make that determination. This new feature is a great enhancement to the system but it will cause a short term disruption. Another disruption is that we will start using the new credit system. The aim of the new system is to better measure the efficiency of different computers and different application versions so that computers are assigned credit in a more consistent way - even across different operating systems or cpu vs gpu. I'm hopeful it will work well. However, this is one area where our development resources just doesn't reflect the diversity and scale of the thousands of volunteer systems that you all provide. As a result, we expect some surprises following the upgrade. Our plan is to monitor what happens and work through issues as they are found. The good news is that we have confidence that the research will continue to be processed correctly during the change. As a preview of the performance of the GPU version, one machine that we have been testing on is a Win7 machine with 6GB RAM, a AMD Phenom II processor oc'd to 3.9GHz and an ATI/AMD 6870 graphics card. On this computer the cpu version runs in about 70 minutes while it runs in about 6 minutes on the gpu version. The first step in moving towards the beta is to get the server code updated in production and ensure that it is stable. Then we will be ready to look at starting the beta testing for gpu. Thank you, knreed. crunching, crunching, crunching. AMD Ryzen 5 2600 6-core Processor with Windows 11 64 Pro. AMD Ryzen 7 3700X 8-Core Processor with Windows 11 64 Pro (part time) ![]() |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
Has the minimum gpu requirements has been drawn or still in the works? To be determined during the beta testing. We have some idea and will try to limit ones we know can't, but there will also have to be a lot of trial and error. This will be a longer than usual beta. |
||
|
|
JEklund2
Advanced Cruncher Finland Joined: Aug 10, 2006 Post Count: 119 Status: Offline Project Badges:
|
Has the minimum gpu requirements has been drawn or still in the works? To be determined during the beta testing. We have some idea and will try to limit ones we know can't, but there will also have to be a lot of trial and error. This will be a longer than usual beta. Any info in the general level: Will single precision cards work or is there any spesific projects etc which would need DP card ? ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Pretty sure the 6870 is not double point, but time will tell.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
2 cards have been mentioned above as having been used in testing:
A Quadro 2000 card is running them in about 12.5 minutes. AMD6870 taking 6 minutes. A quick google says that latter does not support double precision, which says nothing about future projects, would this first get a succession. --//-- |
||
|
|
dkapetansky
Cruncher Joined: Jun 23, 2011 Post Count: 25 Status: Offline Project Badges:
|
Um, briefly, is there a way for me to know whether my device has been classified as "reliable" or "trusted?" (for E2)
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
No, other than seeing production tasks that have short deadline of say 2.8 to 4 days, meaning the device error rate is below 0.2%, there is no public place to see.
--//-- |
||
|
|
|