Message boards : News : New app on acemdbeta with Maxwell support
Author | Message |
---|---|
There's a new application on acemdbeta, version 811 for CUDA 60 which supports the Geforce 750Ti. You'll receive this app if your driver version is 334.21 or greater. | |
ID: 35581 | Rating: 0 | rate:
![]() ![]() ![]() | |
334.x or above is required to support the 750Ti and 750, but I would suggest trying 335.23 if anyone has a GTX750Ti or GTX750 because the driver brings "Enhanced GPU clock offset options for GeForce GTX 750 Ti and GeForce GTX 750". Let's hope Boost isn't still broken. | |
ID: 35586 | Rating: 0 | rate:
![]() ![]() ![]() | |
There's a new application on acemdbeta, version 811 for CUDA 60 which supports the Geforce 750Ti. You'll receive this app if your driver version is 334.21 or greater. Hi, I have driver 334.89 installed, enabled GPUGRID again, but got a cuda5.5 wu, which failed with errorcode -9 (0xfffffffffffffff7) Unknown error number. Beta-apps enabled. Any advice? Alexander | |
ID: 35589 | Rating: 0 | rate:
![]() ![]() ![]() | |
I've updated now to latest driver 335.23, got again a cuda 5.5 wu, which failed. | |
ID: 35590 | Rating: 0 | rate:
![]() ![]() ![]() | |
Your running short queue.... | |
ID: 35591 | Rating: 0 | rate:
![]() ![]() ![]() | |
A CUDA6.0 Windows Beta app is now listed, Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 8.11 (cuda60) 10 Mar 2014 | 10:55:11 UTC http://www.gpugrid.net/apps.php
| |
ID: 35592 | Rating: 0 | rate:
![]() ![]() ![]() | |
Your running short queue.... Right, but the original post did not say anything about short or long runs. Anyway, I've changed my setup, enabled the long runs, enabled gpugrid again and got a ... cuda 55 app. A long run cuda 55. Afterwards I changed my setup to allow beta apps only (because the original message says acemdbeta). Message from server: no tasks available. Alexander | |
ID: 35593 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thank you all for the help, my setup looks like you posted. Will wait to get a cuda 60 app. Alexander | |
ID: 35595 | Rating: 0 | rate:
![]() ![]() ![]() | |
What do you recommend in a mixed system (GTX 580 and GTX 750 Ti)? | |
ID: 35597 | Rating: 0 | rate:
![]() ![]() ![]() | |
What do you recommend in a mixed system (GTX 580 and GTX 750 Ti)? A driver that supports your GTX750Ti, so probably the latest WHQL driver (335.23). ____________ FAQ's HOW TO: - Opt out of Beta Tests - Ask for Help | |
ID: 35601 | Rating: 0 | rate:
![]() ![]() ![]() | |
It would be useful if we could select to run Beta tasks and then either Long or Short tasks if Beta tasks are not available. At present you get both Long and Short if you select to run Other work if Beta's are not available. | |
ID: 35603 | Rating: 0 | rate:
![]() ![]() ![]() | |
Ok, bring them on! | |
ID: 35604 | Rating: 0 | rate:
![]() ![]() ![]() | |
I too have a GTX 750 TI and before I saw this post tried to run GPUGRID and the tasks all failed. I set my preferences to receive Beta and also the acemdbeta task but there are no tasks available. | |
ID: 35645 | Rating: 0 | rate:
![]() ![]() ![]() | |
I've put more WUs on for acemdbeta. | |
ID: 35646 | Rating: 0 | rate:
![]() ![]() ![]() | |
I got a few of these units, so far they are running okay. They take about 2 hours to finish on my computers. Though, we get only 1500 credits for the effort. I don't see any noticeable difference in time to finish, between to cuda 6.0 v8.11 and cuda 5.5 v8.15, so far. | |
ID: 35653 | Rating: 0 | rate:
![]() ![]() ![]() | |
The output files for these units are very large (~45Mb). | |
ID: 35654 | Rating: 0 | rate:
![]() ![]() ![]() | |
On W7 GTX670 I've only seen 2 tasks run on the CUDA6 app, | |
ID: 35659 | Rating: 0 | rate:
![]() ![]() ![]() | |
I am running WinXP on two different PCs, with three GTX 660s (335.xx drivers). One CUDA 4.2 and four CUDA 5.5 work units have completed successfully. However, the only CUDA 6.0 work unit failed right at the start (0 seconds): GPUGRID 8.11 ACEMD beta version (cuda60) 76-MJHARVEY_TEST1999-0-10-RND4103_0 00:00:00 (00:00:00) 3/14/2014 11:45:02 PM 3/14/2014 11:48:03 PM 0.732C + 1NV 0.00 Reported: Computation error (313,) GPUGrid-PC | |
ID: 35660 | Rating: 0 | rate:
![]() ![]() ![]() | |
At present there isn't a Windows beta cuda6 application. Which is a little strange, because there was one last night - I processed task 7929440 using it. A couple of instabilities in the middle, but it completed OK. | |
ID: 35661 | Rating: 0 | rate:
![]() ![]() ![]() | |
Most of my downloads are the beta runs. Maybe only one long run. Just hope that my RAC does not go down because of these betas. I have under GPUGRID preference no beta. | |
ID: 35669 | Rating: 0 | rate:
![]() ![]() ![]() | |
Richard, when GPU's reach ~79 to 80°C some sort of throttling kicks in and the boost usually drops. Whatever is happening on the GPU at this time it causes tasks to become unstable. Fortunately the app can now recover the WU's, but the individuals solution is to increase GPU fan speeds, reducing the temperatures, so GPU's don't reach 79C. It's better than starting and stopping tasks and as it increases GPU longevity, decreases heat and power usage its the generic thing to do when GPU crunching. | |
ID: 35675 | Rating: 0 | rate:
![]() ![]() ![]() | |
The Long Run 8.15 are generating only 54,300 points. I was getting 115,000 before. it seems that the driver 334 is affecting now the scoring. | |
ID: 35676 | Rating: 0 | rate:
![]() ![]() ![]() | |
The recent Long tasks that you ran were shorter than previous tasks: | |
ID: 35677 | Rating: 0 | rate:
![]() ![]() ![]() | |
Richard, when GPU's reach ~79 to 80°C some sort of throttling kicks in and the boost usually drops. Whatever is happening on the GPU at this time it causes tasks to become unstable. Fortunately the app can now recover the WU's, but the individuals solution is to increase GPU fan speeds, reducing the temperatures, so GPU's don't reach 79C. It's better than starting and stopping tasks and as it increases GPU longevity, decreases heat and power usage its the generic thing to do when GPU crunching. In my case, the solution is to preferentially crunch GPUGrid tasks on the (lower, cooler) Device 1. Device 0 crunches other projects. I was doing that manually, and the unexpected Beta cuda60 arrived late in the evening and ran overnight on Device 0. I've now set up a project exclusion for device 0 in cc_config.xml, so that shouldn't happen again. I also agree that there isn't much point in running the Beta tasks using a non-Maxwell card and last November's applications, so I've disabled Beta apps for the time being. Happy to have verified that the cuda60 app does run on pre-Maxwell hardware, and I'll watch out for re-deployment. | |
ID: 35680 | Rating: 0 | rate:
![]() ![]() ![]() | |
Most of the ACEMD beta version v8.15 (cuda55) I got failed immediate after starting. | |
ID: 35684 | Rating: 0 | rate:
![]() ![]() ![]() | |
Alexander, there was a CUDA6 Beta app (in the Beta queue) for Windows, but it's not there now. | |
ID: 35685 | Rating: 0 | rate:
![]() ![]() ![]() | |
Alexander, there was a CUDA6 Beta app (in the Beta queue) for Windows, but it's not there now. Ah, yes and no. I can remember a post that said with driver xxx I will get the cuda 6 wu's. My mistake, I thought, I will get ONLY cuda6 wu's. Anyway, I changed my setup and enabled the short runs and the beta's. I had the long runs enabled before. Let's see what happens. Alexander PS: while writing these lines the download of my first cuda6 wu started! | |
ID: 35686 | Rating: 0 | rate:
![]() ![]() ![]() | |
Many thanks Alexander: | |
ID: 35690 | Rating: 0 | rate:
![]() ![]() ![]() | |
Many thanks Alexander: Glad I could help ! But the question remains; how can I make a setup to get the cuda6 wu's only? This should be a function of the server (as I understand it). | |
ID: 35693 | Rating: 0 | rate:
![]() ![]() ![]() | |
Another question - but first a statement. | |
ID: 35694 | Rating: 0 | rate:
![]() ![]() ![]() | |
Alexander, a couple of questions for you: | |
ID: 35697 | Rating: 0 | rate:
![]() ![]() ![]() | |
Alexander, a couple of questions for you: THX for the quick answer, - yes, I do run igpu apps, two at a time. I'm aware that this reduces memory bandwith usable for the gpu apps, but not that much, that the gpu usage is < 80%. I leave one complete CPU free, so this is usually not a problem. Anyway, it is a beta version and the final version may make better use of the gpu. Let's delay that question. - more than one wu - a 3GB card: GPU-Z reports 300MB used ram , this should not be the bottleneck unless GPU-Z has another understanding what used ram means. Mem controller load says 22%. I have learned that it usually makes sense to run 2 or more wu's when the gpu usage is < 80% and makes little or no sense if usage is > 90%; the overhead eats the gain then. I want to get a deeper understanding, what gpu usage means, how accurate that value is. Without knowing more about this I tend to assume a 95% gpu load equals a 95% power load, but reality shows that this assumption is wrong. I posted my question in the techpowerup forum, hoping that a developer is reading it and finds time to answer my question. Anyway, thanks for the time you take to answer my questions, cheers Alexander | |
ID: 35700 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thanks for answering my questions. | |
ID: 35701 | Rating: 0 | rate:
![]() ![]() ![]() | |
We will see the difference in ~ 4hrs Cheers Alexander | |
ID: 35702 | Rating: 0 | rate:
![]() ![]() ![]() | |
9.5% faster. | |
ID: 35706 | Rating: 0 | rate:
![]() ![]() ![]() | |
So what have we learnt about Maxwell, and what's the situation? | |
ID: 35714 | Rating: 0 | rate:
![]() ![]() ![]() | |
I've tried to test that, but got cuda5.5 tasks only. Answer will come later when cuda6 long runs are available. | |
ID: 35717 | Rating: 0 | rate:
![]() ![]() ![]() | |
Two short questions: | |
ID: 35720 | Rating: 0 | rate:
![]() ![]() ![]() | |
Server Status Will tell you if work is available in a queue, Tasks by application
application unsent in progress avg runtime of last 100 results in h (min-max) users in last 24h
Short runs (2-3 hours on fastest card) 169 1,520 1.46 (0.04 - 9.46) 652
ACEMD beta version 0 76 1.20 (0.22 - 3.62) 93
Long runs (8-12 hours on fastest card) 21 2,017 5.26 (0.07 - 24.00) 615
CPU only app 1 70 0.15 (0.07 - 0.24) 4
Apps Will tell you which queue has a CUDA 6.0 app, Short runs (2-3 hours on fastest card) Platform Version Installation time Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 8.15 (cuda42) 8 Dec 2013 | 15:32:01 UTC Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 8.15 (cuda55) 8 Dec 2013 | 15:32:04 UTC Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 8.15 (cuda60) 14 Mar 2014 | 22:23:53 UTC Linux running on an AMD x86_64 or Intel EM64T CPU 8.00 (cuda42) 26 Aug 2013 | 10:49:37 UTC Linux running on an AMD x86_64 or Intel EM64T CPU 8.00 (cuda55) 26 Aug 2013 | 10:49:36 UTC ACEMD beta version Platform Version Installation time Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 8.15 (cuda42) 14 Nov 2013 | 14:36:32 UTC Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 8.15 (cuda55) 14 Nov 2013 | 14:39:01 UTC Linux running on an AMD x86_64 or Intel EM64T CPU 8.11 (cuda60) 15 Mar 2014 | 0:07:21 UTC Linux running on an AMD x86_64 or Intel EM64T CPU 8.14 (cuda42) 20 Sep 2013 | 21:53:36 UTC Linux running on an AMD x86_64 or Intel EM64T CPU 8.14 (cuda55) 20 Sep 2013 | 21:53:34 UTC Long runs (8-12 hours on fastest card) Platform Version Installation time Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 8.15 (cuda42) 23 Jan 2014 | 14:02:55 UTC Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 8.15 (cuda55) 23 Jan 2014 | 14:02:57 UTC Linux running on an AMD x86_64 or Intel EM64T CPU 8.03 (cuda42) 30 Aug 2013 | 7:52:50 UTC Linux running on an AMD x86_64 or Intel EM64T CPU 8.03 (cuda55) 30 Aug 2013 | 7:52:49 UTC CPU only app Platform Version Installation time Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.05 13 Mar 2014 | 21:53:20 UTC Linux running on an AMD x86_64 or Intel EM64T CPU 1.05 13 Mar 2014 | 21:59:13 UTC The problem is, just because there is a CUDA6 app in the short queue doesn't mean you will get a task that will use that app - you might get tasks that use the CUDA5.5 app. I think the server is supposed to determine your GPU and appropriate apps according to the spec, but this doesn't work. For some reason people with a GTX650Ti seem to be getting lots of CUDA6 work, but those with a GTX750Ti are not. Whatever the system, it's not working. Is there a manual way to force tasks to use the CUDA6 app? ____________ FAQ's HOW TO: - Opt out of Beta Tests - Ask for Help | |
ID: 35721 | Rating: 0 | rate:
![]() ![]() ![]() | |
https://dl.dropboxusercontent.com/u/50246791/gpugrid%20server%20status%20page.PNG | |
ID: 35722 | Rating: 0 | rate:
![]() ![]() ![]() | |
I've just taken the plunge, and obtained a 750Ti: at the moment, it's in host 170387. | |
ID: 35727 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : News : New app on acemdbeta with Maxwell support