Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Ray Tracing on GPU: Performance comparison between the CPU and the Compute Shader with DirectX 11
Blekinge Institute of Technology, School of Computing.
Blekinge Institute of Technology, School of Computing.
2010 (English)Independent thesis Basic level (degree of Bachelor)Student thesis
Abstract [en]

The game industry have always looked for rendering techniques that makes the games as good looking and realistic as possible. The common approach is to use triangles built up by vertices and apply many different techniques to make it look as good as possible. When triangles are used to draw objects, there is always edges and those edges often make the objects look less realistic than desired. To reduce these visible edges the amount of triangles for an object have to be increased, but with more triangles more processing power from the graphics cards is needed. Another way to approach rendering is ray tracing which can render an extremely photo realistic image but to the cost of unbearable low performance if you would use it in a realtime application. The reason raytracing is so slow is the massive amount of calculations that needs to be made. In DirectX 11 a few new shaders where announced and one of them were the compute shader, the compute shader allows you to calculate data on the graphics card which is not bound to the pipeline. The compute shader allows you to use the hundreds of cores that the graphic card has and is therefore well suited for a raytracing algorithm. One application is used to see if the hypothesis is correct. A flag is used to define if the application runs on the CPU and the GPU. The same algorithm is used in both versions. Three test where done on each processing unit to confirm the hypothesis. Three more tests where done on the GPU to see how the performance scaled on the GPU depending on the number of rendered objects. The tests proved throughout that the compute shader performs considerably better than the CPU when running our ray tracing algorithm.

Place, publisher, year, edition, pages
2010. , p. 20
Keywords [en]
Ray Tracing, Compute shader, DirectX, Direct3D, Rendering, Real-time
National Category
Computer Sciences Human Computer Interaction
Identifiers
URN: urn:nbn:se:bth-2514Local ID: oai:bth.se:arkivex801153E74752A38BC1257742005FCB8EOAI: oai:DiVA.org:bth-2514DiVA, id: diva2:829795
Uppsok
Technology
Supervisors
Available from: 2015-04-22 Created: 2010-06-14 Last updated: 2018-01-11Bibliographically approved

Open Access in DiVA

fulltext(2312 kB)2953 downloads
File information
File name FULLTEXT01.pdfFile size 2312 kBChecksum SHA-512
18057c8aa3702cbc068a0b5f38955b80fc6acf8ff4ad08286dabdf439a1a9c46937c9fcb8b5236e40e6c4a4dc313c5ae7511fcf7d6c945ea75b958436b59c4f8
Type fulltextMimetype application/pdf

By organisation
School of Computing
Computer SciencesHuman Computer Interaction

Search outside of DiVA

GoogleGoogle Scholar
Total: 2956 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 556 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf