On 2012/12/28 17:58:13, dvyukov wrote:
Hello mailto:golang-dev@googlegroups.com (cc:
mailto:msolomon@google.com, mailto:sougou@google.com),
I'd like you to review this change to
https://dvyukov%2540google.com%40code.google.com/p/go/
Hello mailto:golang-dev@googlegroups.com (cc:
mailto:msolomon@google.com, mailto:sougou@google.com),
I'd like you to review this change to
https://dvyukov%2540google.com%40code.google.com/p/go/
here.
I have a ray tracer app which consumed memory during run (800x600 image
rendering, 100 rays per pixel, 10 goroutines, 1 goroutine per image row,
GOMAXPROCS=4) starting from 20 megs and ending up with 100 megs or so in
5 minutes of intensive CPU usage. I know there are no allocs in the ray
tracer itself, so it must be stack segments cache. So, I tried your
patch set. It's amazing. Memory consumption went down to 20 megs at the
beginning (same) and 30 megs at the end. And I see no performance
degradation whatsoever.
So, summary:
Before: 20 to 100 megs during run.
After: 20 to 30 megs during run.
In both cases rendering time was 5 minutes 5 seconds.
Так что спасибо огромное за патч, я как раз хотел выяснить от чего такое
поведение у проги.
https://codereview.appspot.com/6997052/
