Donate To Seti@HomeSeti@Home optimized science apps and information
 
Welcome, Guest. Please login or register.
15 Sep 2014, 05:27:25 am

Login with username, password and session length
 
» Home
» Forums
» Downloads
» FAQ
» News

» Search site
 
 
 
If you've registered already but never got your activation email, please click here.
 
 
 1   Optimized Seti@Home apps / Discussion Forum / Re: AstroPulse v7 performance illustration  on: 13 Sep 2014, 05:46:06 pm 
Started by Raistmer | Last post by Raistmer
And another update. Now due to long mess for CPU app selection on beta I collected many GPU tasks paired with 7.00 plain CPU app.
1 core was idle still. But as one can see, sometimes leaving 1 core free not enough. Maybe there were moments of non-BOINC host activity, maybe just unlocky OS decision, but elapsed times in this config definitely bigger sometimes than with all cores busy but -cpu_lock enabled.

Data sets now not compaable though, for idle core much more points aquired.

Next will be 2 GPU tasks per HD6950 with -cpu_lock enabled and all CPU cores busy again.

 2   Optimized Seti@Home apps / Discussion Forum / SETI MultiBeam performance on Android devices  on: 13 Sep 2014, 05:17:40 pm 
Started by Raistmer | Last post by Raistmer
Today I found time to prepare graph for one of my G-tab devices.
It shows performance of different MB7 apps this devic ran through last year or so.
As one can see Mateusz's app outperforms older stock builds. After those there was big period when all stock buiulds were incompatible with this device. 7.28 is compatible, but no data available so far.


 3   Optimized Seti@Home apps / GPU crunching / Re: Deprecated features in the latest/next Cuda toolkit  on: 02 Sep 2014, 10:37:56 pm 
Started by Claggy | Last post by arkayn
Considering we know that 64-bit CUDA apps are slower than 32-bit CUDA apps, that is just plain ridiculous.

 4   Optimized Seti@Home apps / GPU crunching / Re: Deprecated features in the latest/next Cuda toolkit  on: 02 Sep 2014, 05:18:48 pm 
Started by Claggy | Last post by Urs Echternacht
Are they crazy Huh
They have quite a long breath ...

 5   Optimized Seti@Home apps / GPU crunching / Re: Deprecated features in the latest/next Cuda toolkit  on: 02 Sep 2014, 04:17:28 pm 
Started by Claggy | Last post by Raistmer
Are they crazy Huh

 6   Optimized Seti@Home apps / GPU crunching / Deprecated features in the latest/next Cuda toolkit  on: 02 Sep 2014, 02:35:28 pm 
Started by Claggy | Last post by Claggy
For anyone who hasn't seen it, this came up on the Boinc dev board yesterday:

http://boinc.berkeley.edu/dev/forum_thread.php?id=9588

Quote
(Mac OS X) Support for 32-bit CUDA and OpenCL Applications on Mac OS X
 Developing and running 32-bit CUDA and OpenCL applications on Mac OS X platforms is no longer supported in the CUDA Toolkit and in the CUDA Driver. Legacy 32-bit CUDA and OpenCL applications will not run on this version of the CUDA Driver on Mac OS X platforms.

and:

Quote
Targeting sm_10 (G80) for CUDA Applications
The CUDA Toolkit no longer supports the sm_10 target architecture (the G80 architecture) for CUDA and OpenCL applications.

and:

http://boinc.berkeley.edu/dev/forum_thread.php?id=9588&postid=55766
Quote
Well, reading through there, the problems are a little bigger than just broken applications for Mac users. It'll be broken applications for A LOT of GPUs, as Deprecated Features writes:
The following features are deprecated in the current release of the CUDA software. The features still work in the current release, but their documentation may have been removed, and they will become officially unsupported in a future release. We recommend that developers employ alternative solutions to these features in their software.

Tesla and Quadro Products and CUDA Toolkit on 32-bit Windows Platforms
Support for the CUDA Toolkit on 32-bit Windows platforms is deprecated, as is support for Tesla and Quadro products for the CUDA driver on 32-bit Windows platforms. Additionally, on 64-bit Windows platforms, support for the following features for 32-bit CUDA and OpenCL applications is deprecated from the CUDA driver and CUDA toolkit, as appropriate:

Tesla and Quadro products
CUDA Toolkit scientific libraries, including cuBLAS, cuSPARSE, cuFFT, cuRAND, and NPP
Thrust
CUDA samples

This deprecation notice doesn't impact any 64-bit components.

Linux RHEL 5 and CentOS 5 Support
Support for CUDA on the RHEL 5 and CentOS 5 Linux distributions is deprecated in this CUDA release and will be dropped in a future release. We recommend that users and developers migrate to RHEL 6, which is supported in the current and future releases.

Support for sm_10, sm_11, sm_12, and sm_13 Architectures
The sm_10 architecture is deprecated within the CUDA Driver, and the sm_11, sm_12, and sm_13 architectures are deprecated within the CUDA Toolkit and the CUDA Driver. Support for these architectures will be removed in the next major version of the CUDA Toolkit and Driver. Note that support for the sm_10 architecture has already been removed from the CUDA Toolkit.

The latter means that any GPU with compute capability 1.0, 1.1, 1.2 and 1.3 on https://developer.nvidia.com/cuda-gpus will get deprecated in the future. This includes the GTX2xx series.

http://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#unsupported-features

Claggy

 7   Optimized Seti@Home apps / GPU crunching / Re: New Video Card  on: 01 Sep 2014, 12:39:44 pm 
Started by TouchuvGrey | Last post by juan BFB
Before you try anything may i sugest you to read this article from Vyper“s site, it“s helps a lot:

http://vyper.kafit.se/wp/index.php/2011/02/04/running-different-nvidia-architectures-most-optimal-at-setihome/

 8   Optimized Seti@Home apps / GPU crunching / Re: New Video Card  on: 01 Sep 2014, 11:46:49 am 
Started by TouchuvGrey | Last post by TouchuvGrey
Thank you again Juan, i will likely have
more questions when i am setting everything up.    Smiley

 9   Optimized Seti@Home apps / GPU crunching / Re: New Video Card  on: 01 Sep 2014, 11:38:47 am 
Started by TouchuvGrey | Last post by juan BFB
I use that to exactly to make a 580 (Fermi) work with a 670 (Keppler) on the same host since each one uses a diferent CUDA version. Works perfect.

If you run AP and the newer builds you have another good reason to do that since they use a diferent command line to optimize each GPU .

BTW The secondary "good" efect is your cache size limit will automaticaly rise from 200 for both GPU“s when you run 1 instance to 400 if you run 2 instances and you could control each cache size separately.


 10   Optimized Seti@Home apps / GPU crunching / Re: New Video Card  on: 01 Sep 2014, 09:53:19 am 
Started by TouchuvGrey | Last post by TouchuvGrey
Thank you Juan, i had not even
considered that option.   Embarrassed

Return to the board index.

Quote!
Left to themselves, things tend to go from bad to worse.
- Murphy's Law

 
Site Statistics
Total Members:96
Total Posts:54,986
Total Topics:1,556
Downloads
..Some PHP stuff ToDo
Pages served
Today:809
Total:19,851,547
(since 6/26/2006)
Latest Member:
Just Will Lite
 
 
Seti@Home optimized science apps and information | Powered by Enigma 2.0 (RC1).
© 2003-2014, LSP Dev Team. All Rights Reserved.
Seti@Home optimized science apps and information Forums | Powered by SMF.
© 2005, Simple Machines LLC. All Rights Reserved.
Powered by MySQL Powered by PHP Valid XHTML 1.0! Valid CSS!