GPU

Message boards : Number crunching : GPU

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile [VENETO] boboviz

Send message
Joined: 1 Dec 05
Posts: 1994
Credit: 9,523,781
RAC: 8,309
Message 68973 - Posted: 1 Jan 2011, 21:34:24 UTC - in response to Message 68928.  

http://en.wikipedia.org/wiki/CUDA#Limitations

"The bus bandwidth and latency between the CPU and the GPU may be a bottleneck."



Why not OpenCL??

http://boinc.fzk.de/poem/forum_thread.php?id=384
ID: 68973 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 68976 - Posted: 1 Jan 2011, 22:04:28 UTC

The bottleneck mentioned is physically in the hardware. OpenCL is not hardware and so does nothing to relieve the bottleneck.
Rosetta Moderator: Mod.Sense
ID: 68976 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
mikey
Avatar

Send message
Joined: 5 Jan 06
Posts: 1895
Credit: 9,132,201
RAC: 5,104
Message 68980 - Posted: 2 Jan 2011, 13:11:20 UTC - in response to Message 68972.  

The problem seem to be that the Rosetta calculations do not fit into a gpu's memory, meaning there would be a TON of swapping back and forth negating any advantage of using the gpu in the first place.


The problem is about the difference beetween memories (for example DDR3 and GDDR5) or the amount of memory on graphic board (the last ATI and NVIDIA cards have a LOT of memory)??


Alot by whose counting, 1 gb of memory is not alot by cpu standards, but yes it is alot by gpu standards. Although since not everyone has that much memory on their gpu's the app must be tailored to fit many gpu's so it must be sized to fit in as little as 256 mb of memory, the standard for most gpu cards of just a few years ago.
ID: 68980 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 1 Dec 05
Posts: 1994
Credit: 9,523,781
RAC: 8,309
Message 68985 - Posted: 2 Jan 2011, 20:57:34 UTC - in response to Message 68976.  
Last modified: 2 Jan 2011, 20:58:14 UTC

The bottleneck mentioned is physically in the hardware.


Bottleneck between processor and memory? Is this the solution??
http://sites.amd.com/us/fusion/apu/Pages/fusion.aspx
ID: 68985 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
mikey
Avatar

Send message
Joined: 5 Jan 06
Posts: 1895
Credit: 9,132,201
RAC: 5,104
Message 68988 - Posted: 3 Jan 2011, 11:52:01 UTC - in response to Message 68985.  

The bottleneck mentioned is physically in the hardware.


Bottleneck between processor and memory? Is this the solution??
http://sites.amd.com/us/fusion/apu/Pages/fusion.aspx


Sounds like a way to make us buy new stuff because our current stuff won't work with this! Yes it could be faster but only if they design it that way, if they just stick a gpu on the same die as a cpu, they are not making it better just smaller. Right now one of the problems in pc's is the heat generated by the cpu and gpu, if you stick all that heat in one place you must design better air flow too!!
ID: 68988 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 68994 - Posted: 3 Jan 2011, 16:32:41 UTC

Right, getting two components closer together minimizes the time for them to interoperate, but you still have to essentially page fault everything to the GPU for it to process. So, GPU memory is still the primary constraint.
Rosetta Moderator: Mod.Sense
ID: 68994 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 1 Dec 05
Posts: 1994
Credit: 9,523,781
RAC: 8,309
Message 68995 - Posted: 3 Jan 2011, 17:51:36 UTC - in response to Message 68994.  

Right, getting two components closer together minimizes the time for them to interoperate, but you still have to essentially page fault everything to the GPU for it to process. So, GPU memory is still the primary constraint.


Yeap, but in AMD (and INTEL) roadmap this is only the first step to a deeper integration between cpu and gpu components...

ID: 68995 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Previous · 1 · 2

Message boards : Number crunching : GPU



©2024 University of Washington
https://www.bakerlab.org