Forum > GPU crunching
AK V8 + CUDA MB team work mod
Raistmer:
Version for SSE2 only CPUs added.
MAOJC:
--- Quote from: Raistmer on 04 Feb 2009, 01:19:52 pm ---
--- Quote from: MAOJC on 04 Feb 2009, 01:08:38 pm ---
--- Quote from: Raistmer on 26 Jan 2009, 11:57:38 am ---
--- Quote from: Slawek on 26 Jan 2009, 11:51:58 am ---AMD SSE3 (X2 Athlon ) working on this build ?
--- End quote ---
No, will do SSE3 soon.
BTW, does anyone need SSE2 and low ?
That is, does anybody have SSE2-only CPU with CUDA-enabled GPU ?
--- End quote ---
Waiting with baited breath. ;)
Yep have old Opteron (SSE2) OC'd with a 9600 GTX under XP
So the AMD file on the first page will now work?
--- End quote ---
No, I will assemble working package and put on first page soon.
Currently only SSE3 and up supported. (provided AP is SSE3 one)
--- End quote ---
Grey Shadow:
Just noticed one strange thing.
If BOINC (I use 6.4.5) downloads new workunits with shorter deadline it stops crunching previous WUs and switches to new ones. But GPU-crunching doesn't start - all workunits are processed only by CPU cores. As a result GPU stays idle till all short-deadline workunits are finished and computation of previous ones resumes.
I assume that it happens because when GPU crunching starts GPU-thread became fixed to parcitular workunit and nothing can be changed before this workunit is finished (completed or aborted). I don't know if such behavior is special for your 8a mod or it also affects stock app, but it will be really great of you defeat it :)
Raistmer:
--- Quote from: Grey Shadow on 04 Feb 2009, 02:04:00 pm ---Just noticed one strange thing.
If BOINC (I use 6.4.5) downloads new workunits with shorter deadline it stops crunching previous WUs and switches to new ones. But GPU-crunching doesn't start - all workunits are processed only by CPU cores. As a result GPU stays idle till all short-deadline workunits are finished and computation of previous ones resumes.
I assume that it happens because when GPU crunching starts GPU-thread became fixed to parcitular workunit and nothing can be changed before this workunit is finished (completed or aborted). I don't know if such behavior is special for your 8a mod or it also affects stock app, but it will be really great of you defeat it :)
--- End quote ---
It's specific to V8 approach of handling GPU, stock and V7 will not suffer from it.
Restart BOINc when it happens and consider to work in download big cache->suspend network->process tasks->resume network->renew cache mode with V8. There is no way to repair this but forbid BOINC to with to another task untill it finishes current one.
Grey Shadow:
Thank you for your response.
I'll try to turn off network communications when I am unable to control BOINC for long time.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version