janvanbergen

The GPU I currently use is my laptop's 845m, so I don't think my performance numbers are that representative

I'm mostly trying to keep the pathtracer simple and performant, so for this reason I would rather not implement bidirectional methods. However, I may end up implementing path guiding instead in order to better sample caustics etc.

I sample the lights proportional to their area times intensity. This is very much less than optimal for scenes with many lights.

As far as opencl goes, I don't have much experience with it so I cant really comment. For my GPU code I do tend to prefer a C-ish coding style, although I still use templates etc here and there.

SOA vs AOS mostly comes down to whatever access pattern you use on the data. On the CPU you mostly have to worry about the cache/prefetcher, on the GPU its more important to get coalesced vector loads in order to make maximum use of bandwidth

Compiler written in C for a custom programming language that targets x64 assembly (NASM). Several examples included in the repository.