We’re rewarding the question askers & reputations are being recalculated! Read more.
    Bumped by Community user
    Tweeted twitter.com/#!/StackCodeReview/status/637676461709770752
6 added 93 characters in body
source | link

For those who don't know Golang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutine in Go). If I have c <- m that means "send this message via this channel". Both the brute force and the BVH use this primitive so thats probably not the reason for the slowdown.

For those who don't know Golang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutine in Go). If I have c <- m that means "send this message via this channel".

For those who don't know Golang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutine in Go). If I have c <- m that means "send this message via this channel". Both the brute force and the BVH use this primitive so thats probably not the reason for the slowdown.

5 added 3 characters in body; edited title
source | link

bounding Bounding volume hierarchy too slow?

So I'm building a bounding volume hierarchy in golangGolang. I can tell my code works because I did some test on it and it gives the same results as the brute force implementation (brute force is to test all possibilities, in \$O(n^2)\$). 

My problem is that the code is slower thenthan the brute force implementation (not by that much but enough to make me wonder why I bothered to implement this in the first place), maybe. Maybe that's normal, but I would like the opinion of my peers on this.
For

For those who don't know golangGolang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutine in Go). If I have c <- m that means "send this message via this channel".

Is there something obvious in my implementation that would make thsithis super slow  ? Am I doing something twice or anything that could add a lot more work to achieve the same result  ?

bounding volume hierarchy too slow?

So I'm building a bounding volume hierarchy in golang. I can tell my code works because I did some test on it and it gives the same results as the brute force implementation (brute force is to test all possibilities, in \$O(n^2)\$). My problem is the code is slower then the brute force implementation (not by that much but enough to make me wonder why I bothered to implement this in the first place), maybe that's normal, but I would like the opinion of my peers on this.
For those who don't know golang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutine in Go). If I have c <- m that means "send this message via this channel".

Is there something obvious in my implementation that would make thsi super slow  ? Am I doing something twice or anything that could add a lot more work to achieve the same result  ?

Bounding volume hierarchy

I'm building a bounding volume hierarchy in Golang. I can tell my code works because I did some test on it and it gives the same results as the brute force implementation (brute force is to test all possibilities, in \$O(n^2)\$). 

My problem is that the code is slower than the brute force implementation (not by that much but enough to make me wonder why I bothered to implement this in the first place). Maybe that's normal, but I would like the opinion of my peers on this.

For those who don't know Golang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutine in Go). If I have c <- m that means "send this message via this channel".

Is there something obvious in my implementation that would make this super slow? Am I doing something twice or anything that could add a lot more work to achieve the same result?

4 Minor edits
source | link

So I'm building a bounding volume hierarchy in golang. I can tell my code works because I did some test on it and it gives the same results as the brute force implementation (brute force is to test all possibilities, in \$O(n^2)\$). My problem is the code is slower then the brute force implementation (not by that much but enough to make me wonder why iI bothered to implement this in the first place), maybe that's normal, but I would like the opinion of my peers on this.
For those who don't know golang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutinegoroutine in Go). If I have c <- m that means "send this message via thsi channelthis channel".

So I'm building a bounding volume hierarchy in golang. I can tell my code works because I did some test on it and it gives the same results as the brute force implementation (brute force is to test all possibilities, in \$O(n^2)\$). My problem is the code is slower then the brute force implementation (not by that much but enough to make me wonder why i bothered to implement this in the first place), maybe that's normal but I would like the opinion of my peers on this.
For those who don't know golang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutine in Go). If I have c <- m that means "send this message via thsi channel.

So I'm building a bounding volume hierarchy in golang. I can tell my code works because I did some test on it and it gives the same results as the brute force implementation (brute force is to test all possibilities, in \$O(n^2)\$). My problem is the code is slower then the brute force implementation (not by that much but enough to make me wonder why I bothered to implement this in the first place), maybe that's normal, but I would like the opinion of my peers on this.
For those who don't know golang but would still like to take a look. a chan is a primitive to send/receive messages from other threads (we call thread, goroutine in Go). If I have c <- m that means "send this message via this channel".

3 added 239 characters in body; edited title
source | link
2 add jax bling
source | link
1
source | link