Forum > GPU crunching

AK V8 + CUDA MB team work mod

<< < (12/51) > >>

Raistmer:

--- Quote from: wickedguy on 31 Jan 2009, 05:05:45 pm ---
--- Quote from: Raistmer on 31 Jan 2009, 04:11:04 pm ---Yes, it shouldn't, read again first post.
For dual GPU configs V7x of combo is more suitable, V8x for single GPU only.

--- End quote ---

Yup I read it, and i used it! But I cant get any more AP Wu since the last 3-4days, So i switched to V8x for that reason  ;D

--- End quote ---
Yeah, unfortunately both approaches have their own flaws. Hope sooner or later BOINC will do shceduling work by itself as it should be.
For now I can recommend switching to V7x combo while doing another CPU-based project like Einstein. That way you will use both GPU cards and do good things with your CPU also.
AP work is now ceased cause new AP version in testing...

YukonTrooper:

--- Quote from: Raistmer on 31 Jan 2009, 02:07:22 am ---Look at link you provided. It points on CUDA processed task.
ADDON: form stderr of your result:
Cuda error 'cudaMemcpyToSymbol(cudaAcc_GaussFit_settings, (void*) &settings, sizeof(settings))' in file 'd:/BTR/seticuda/seti_boinc/client/cuda/cudaAcc_gaussfit.cu' in line 454 : invalid device symbol.

The answer is the same - update to 18x.xx drivers.

--- End quote ---
I noticed that, but I didn't think anything of it because it was the AK V8 processes failing; however, I updated to 180.xx and I now see how everything works.  MB works but CUDA doesn't show up in Boinc Manager.  This is normal, correct?  Can I suspend CUDA without suspending anything else for when I play games, or do I have to cancel the whole project?

Josef W. Segur:

--- Quote from: Raistmer on 31 Jan 2009, 05:19:43 pm ---...
AP work is now ceased cause new AP version in testing...
--- End quote ---

The ap_splitters at main finished splitting all the data the project had on hand, a hoped-for shipment from Arecibo didn't arrive Friday, and the HPSS which has the reserve stock of unsplit data was being upgraded so Matt couldn't get more data. If they've also decided to not split AP work when there's some available, that's good too.
                                                                                   Joe

Raistmer:

--- Quote from: Josef W. Segur on 01 Feb 2009, 01:38:29 am ---
--- Quote from: Raistmer on 31 Jan 2009, 05:19:43 pm ---...
AP work is now ceased cause new AP version in testing...
--- End quote ---

The ap_splitters at main finished splitting all the data the project had on hand, a hoped-for shipment from Arecibo didn't arrive Friday, and the HPSS which has the reserve stock of unsplit data was being upgraded so Matt couldn't get more data. If they've also decided to not split AP work when there's some available, that's good too.
                                                                                   Joe

--- End quote ---
It's offtopic to current thread but too curious not to ask :)
Is data set that possible to process with AP so smaller than MB one ?? We do MB many years already - do that huge data array not suitable for AP ?

Raistmer:

--- Quote from: YukonTrooper on 31 Jan 2009, 07:39:26 pm ---I noticed that, but I didn't think anything of it because it was the AK V8 processes failing; however, I updated to 180.xx and I now see how everything works.  MB works but CUDA doesn't show up in Boinc Manager.  This is normal, correct?  Can I suspend CUDA without suspending anything else for when I play games, or do I have to cancel the whole project?

--- End quote ---

Reread first post once more ;D
There is NO separate CUDA app from BOINC point of view. BOINC doesn't know anything about this CUDA app. It's modified AK_v8 who will call CUDA and who will fail for BOINC if CUDA fails.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version