kid0m4n

12 ms·

91.
by kid0m4n 13y ago
gccgo should give better numbers with Go as well. I am guess we pick one and stick with it. I don't mind trying Intel's compiler though
92.
by kid0m4n 13y ago
Fair enough... let me do a quick test with -O2 and see how that fares
93.
by kid0m4n 13y ago
Hey, possible to optimize the code and send over a PR? I would love to rerun the benchmarks with a optimized Rust version and my rust is totally rusty (pun intended :P)
94.
by kid0m4n 13y ago
I was looking at the Rust-dev mailing list before going to sleep :) I would argue that it is not cheating "anymore" as both the Go and C++ version are now equal. In fact, I wanna compare how Rust performs in this exact same test w
95.
by kid0m4n 13y ago
Author of the article here It helps in finding out details of what the compiler (Xg) thinks of various funcs inlining applicability (is that even a word?)
96.
Go vs C++: Ray tracer (part 3)(kidoman.com)
115 points by kid0m4n 13y ago|60 comments
97.
by kid0m4n 13y ago
C++ multi threaded: https://kidoman.com/programming/go-getter-part-3.html
98.
by 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
99.
by kid0m4n 13y ago
I am trying my hand at a few things... will keep this in mind
100.
by kid0m4n 13y ago
"Go Getter" ?
101.
by 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/6
102.
Business Card Ray Tracer: Go vs C++(kidoman.com)
9 points by kid0m4n 13y ago|9 comments
103.
by kid0m4n 13y ago
The same thing, implemented in Go: https://github.com/kid0m4n/gorays
104.
by kid0m4n 13y ago
True, but that would apply only when you are dealing with tasks which are likely to stall. In this particular case, we are doing CPU intensive calculations in tight loops and no I/O. I scaled the number of goroutines from 1 to 8 (total
105.
by kid0m4n 13y ago
The original was running upto 8 goroutines (my runtime.NumCPU() is 8.)
106.
by kid0m4n 13y ago
Welcome! Now have a look at this: https://github.com/logicchains/Levgen-Parallel-Benchmarks/pu...
107.
by kid0m4n 13y ago
Thanks :P And now an even faster version for your perusal: https://github.com/logicchains/Levgen-Parallel-Benchmarks/pu... > 120 ms improvement over the origin implementation
108.
by kid0m4n 13y ago
Have sent in a pull request: https://github.com/logicchains/Levgen-Parallel-Benchmarks/pu... Go performance improves from ~470 ms to ~360 ms on my Quad core MBP 15 (Late 2011)
109.
by kid0m4n 13y ago
You are talking about Java right?</s>
110.
by kid0m4n 13y ago
Looks like a Major DDOS attack! <naive>Why attack a open source repository?</naive>
111.
by kid0m4n 13y ago
The submitted URL was down a minute ago. Its working now, while the main page ( https://github.com/ ) is still down
112.
Github is down (main site, *.github.io opening now)(robfig.github.io)
13 points by kid0m4n 13y ago|6 comments
113.
Why Sublime Text?(kidoman.com)
1 points by kid0m4n 13y ago|0 comments
114.
by kid0m4n 14y ago
And that is "still" the case
115.
by kid0m4n 14y ago
Regex pattern gone wrong?
116.
by kid0m4n 14y ago
+1 to that. Or a status.news.ycombinator.com
117.
by kid0m4n 14y ago
Rake, for example, was perpetually stuck in the 0.x version because the author just mentally mapped the "0." part away. It recently moved to version 10.x :)