GTX Titan

Started by elricm, March 12, 2013, 07:07:38 AM

Previous topic - Next topic
Hi there,

i have my GTX Titan running for several days ... the per day RAC is dissapointing (ca. 33k WU)  :o

http://stats.free-dc.org/stats.php?page=host&proj=sah&hostid=6775938

I am using the newest beta driver of NVIDIA (314.14) and x41zc_Winx64_cuda50


10-Mar-2013 23:20:22 [---] No config file found - using defaults
10-Mar-2013 23:20:22 [---] Starting BOINC client version 7.0.28 for windows_x86_64
10-Mar-2013 23:20:22 [---] log flags: file_xfer, sched_ops, task
10-Mar-2013 23:20:22 [---] Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
10-Mar-2013 23:20:22 [---] Data directory: C:\ProgramData\BOINC
10-Mar-2013 23:20:22 [---] Running under account Volker
10-Mar-2013 23:20:22 [---] Processor: 8 GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Family 6 Model 58 Stepping 9]
10-Mar-2013 23:20:22 [---] Processor: 256.00 KB cache
10-Mar-2013 23:20:22 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 syscall nx lm vmx smx tm2 popcnt aes pbe
10-Mar-2013 23:20:22 [---] OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00)
10-Mar-2013 23:20:22 [---] Memory: 3.95 GB physical, 7.90 GB virtual
10-Mar-2013 23:20:22 [---] Disk: 465.66 GB total, 410.97 GB free
10-Mar-2013 23:20:22 [---] Local time is UTC +1 hours
10-Mar-2013 23:20:22 [---] NVIDIA GPU 0: GeForce GTX TITAN (driver version 314.14, CUDA version 5.0, compute capability 3.5, 4096MB, 8384512MB available, 4707 GFLOPS peak)
10-Mar-2013 23:20:22 [---] OpenCL: NVIDIA GPU 0: GeForce GTX TITAN (driver version 314.14, device version OpenCL 1.1 CUDA, 6144MB, 8384512MB available)
10-Mar-2013 23:20:22 [SETI@home] Found app_info.xml; using anonymous platform
10-Mar-2013 23:20:22 [SETI@home] URL http://setiathome.berkeley.edu/; Computer ID 6775938; resource share 100
10-Mar-2013 23:20:22 [SETI@home] General prefs: from SETI@home (last modified 19-Jan-2013 22:22:34)
10-Mar-2013 23:20:22 [SETI@home] Host location: none
10-Mar-2013 23:20:22 [SETI@home] General prefs: using your defaults


and


<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b2_win_x64_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AK_v8b2_win_x64_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AK_v8b2_win_x64_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r409_SSE.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41zc_win32_cuda50.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>mbcuda.cfg</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.080000</avg_ncpus>
<max_ncpus>0.080000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.25</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.080000</avg_ncpus>
<max_ncpus>0.080000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.25</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.080000</avg_ncpus>
<max_ncpus>0.080000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.25</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.080000</avg_ncpus>
<max_ncpus>0.080000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.25</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.080000</avg_ncpus>
<max_ncpus>0.080000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.25</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.080000</avg_ncpus>
<max_ncpus>0.080000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.25</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
</app_info>


and i set mbcuda.cfg settings with the following content:


[mbcuda]
processpriority = abovenormal
pfblockspersm = 16
pfperiodsperlaunch = 200



I expected a per-Day of 50-60k WU. Whats is wrong ? Is this a Kepler issue ?

Please help

Regards
ElricM



Quote from: elricm on March 12, 2013, 07:07:38 AM
Hi there,

i have my GTX Titan running for several days ... the per day RAC is dissapointing (ca. 33k WU)  :o

http://stats.free-dc.org/stats.php?page=host&proj=sah&hostid=6775938

I am using the newest beta driver of NVIDIA (314.14) and x41zc_Winx64_cuda50


I expected a per-Day of 50-60k WU. Whats is wrong ? Is this a Kepler issue ?

Please help

Regards
ElricM
Nothing is wrong, you'll have to wait weeks for your RAC to get to that level, RAC is a rolling average, it doesn't instantly increase, each Wu you do has to be done by another computer too,
so you're waiting on your wingmen to complete their Wu's, then those Wu's have to validate, give it time and your RAC will increase.

Claggy

Hmm, i understand your argument but, if you have a look on the graphs at http://stats.free-dc.org/stats.php?page=hostbycpid&cpid=ee1cbaa120f830dba3ee3efb8b330470, it is not really "rocking"  :-\

March 13, 2013, 03:56:59 PM #3 Last Edit: March 13, 2013, 04:19:04 PM by Jason G
One thing you need to keep an eye on is if your pending list is growing, staying around the same, or shrinking.  Ultimately for things to stabilise on a high volume card/system, you're going to need continuous running.  One the other aspect is that it's still early days for Titan. A lot isn't known yet.  Factors I *expect* to be very important with these and existing builds are that video memory clock first, and core clock second.  After that, there are special instructions for 'reductions', a major bottleneck in some portions of early & later Cuda builds.  I have no estimates on the potential impact here yet, though they might be significant in future builds.

If short, with a new architecture it can take 6-18 months to find its lifecycle peak.  Some of that transition time has been shortened by implementation of self-scaling code in later apps, though there are other technologies here yet to be explored

Jason
It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change.
Charles Darwin
---
Chaos: When the present determines the future, but the approximate present does not approximately determine the future.
Edward Lorenz

Currently the pending list is staying around the same, it is comparable with another system i have running with one GTX 670. That is frustating for a card which costs 985 €.  :'(
I agree with you, maybe it is to early to use this card. I will play around with Memory clock and core clock, perhaps it is possible to activate the "turbo boost" .
Thanks for helping!

ElricM

There is mention of a specific OpenCL fix for TITAN in the 314.21 beta driver release notes:

Quote[GeForce GTX TITAN]: Application crashes or a TDR occurs when running
applications that use OpenCL. [1237211]

Powered by EzPortal