3 ms·

Business Card Ray Tracer: Go vs C++

9 points by kid0m4n 13y ago

diydsp 13y ago
Umm... talk about missing the point. The C++ version fits onto a business card. it's 35 lines by 37 characters wide. (1295 bytes) The Go version is 229 lines (6.5x as long) and 4255 bytes long (3.2x as long). Fit that on a business card... Your title should be "Go program optimized for speed faster than C++ program optimized for code size" and you should stop trying provoke people with false comparisons.
- niuzeta 13y ago
  This. the title "Go better" turned me right away.
  - kid0m4n 13y ago
    "Go Getter" ?
- kid0m4n 13y ago
  I am happy to rerun the benchmarks (single threaded and multi threaded) with a optimized C++ version. Sadly, been a while since I last worked on C++ The base C++ version, for reference: https://gist.github.com/kid0m4n/6680629 https://gist.github.com/kid0m4n/6680629 But its never going to be apples-to-apples comparison. Given the different feature sets of either platform But this definitely shows that Go performance is in the same ballpark though.
  - DerekL 13y ago
    I'd need to use a profiler to be sure, but the first thing I'd try is to replace the printf call for each pixel with an fwrite.
    - kid0m4n 13y ago
      I am trying my hand at a few things... will keep this in mind
- kid0m4n 13y ago
  I have rerun the benchmarks now after optimizing the C++ version the best "I" could: https://kidoman.com/programming/go-getter-part-2.html https://kidoman.com/programming/go-getter-part-2.html
  - diydsp 13y ago
    IIUC, the diff b/t go and most languages is that go spawns threads through a slicing mechanism to leverage multiple cores, right?! That's why the go version speeds up when run on multiple-core systems...right? So, I added pthreads to the ray-tracer program: http://pastebin.com/6V5JYyZG http://pastebin.com/6V5JYyZG Included in the paste are the execution times on my lowly dual-core laptop. Spawning more threads speeds up the program. I would be curious to see how it scales to more cores on modern CPUs. If you have a chance, won't you please give it a try on your system and let me know how changing the number of threads affects execution time? For anyone who wants to try pthreads in C, the simplest example and progressions I could find were here: http://cs.gmu.edu/~white/CS571/Examples/pthread_examples.html http://cs.gmu.edu/~white/CS571/Examples/pthread_examples.htm...
    - kid0m4n 13y ago
      C++ multi threaded: https://kidoman.com/programming/go-getter-part-3.html https://kidoman.com/programming/go-getter-part-3.html

9 points by kid0m4n 13y ago

Umm... talk about missing the point. The C++ version fits onto a business card. it's 35 lines by 37 characters wide. (1295 bytes) The Go version is 229 lines (6.5x as long) and 4255 bytes long (3.2x as long). Fit that on a business card... Your title should be "Go program optimized for speed faster than C++ program optimized for code size" and you should stop trying provoke people with false comparisons.

niuzeta 13y ago
This. the title "Go better" turned me right away.
- kid0m4n 13y ago
  "Go Getter" ?
kid0m4n 13y ago
I am happy to rerun the benchmarks (single threaded and multi threaded) with a optimized C++ version. Sadly, been a while since I last worked on C++ The base C++ version, for reference: https://gist.github.com/kid0m4n/6680629 https://gist.github.com/kid0m4n/6680629 But its never going to be apples-to-apples comparison. Given the different feature sets of either platform But this definitely shows that Go performance is in the same ballpark though.
- DerekL 13y ago
  I'd need to use a profiler to be sure, but the first thing I'd try is to replace the printf call for each pixel with an fwrite.
  - kid0m4n 13y ago
    I am trying my hand at a few things... will keep this in mind
kid0m4n 13y ago
I have rerun the benchmarks now after optimizing the C++ version the best "I" could: https://kidoman.com/programming/go-getter-part-2.html https://kidoman.com/programming/go-getter-part-2.html
- diydsp 13y ago
  IIUC, the diff b/t go and most languages is that go spawns threads through a slicing mechanism to leverage multiple cores, right?! That's why the go version speeds up when run on multiple-core systems...right? So, I added pthreads to the ray-tracer program: http://pastebin.com/6V5JYyZG http://pastebin.com/6V5JYyZG Included in the paste are the execution times on my lowly dual-core laptop. Spawning more threads speeds up the program. I would be curious to see how it scales to more cores on modern CPUs. If you have a chance, won't you please give it a try on your system and let me know how changing the number of threads affects execution time? For anyone who wants to try pthreads in C, the simplest example and progressions I could find were here: http://cs.gmu.edu/~white/CS571/Examples/pthread_examples.html http://cs.gmu.edu/~white/CS571/Examples/pthread_examples.htm...
  - kid0m4n 13y ago
    C++ multi threaded: https://kidoman.com/programming/go-getter-part-3.html https://kidoman.com/programming/go-getter-part-3.html