That's surprising. You don't happen to have a bisect handy, do you? (If not, I can run one.)

I was planning to bisect tomorrow; laptop otherwise occupied today. Go for it.

Bisect started

cd runtime && mkdir -p issue-28678 && pl benchmany -d issue-28678 -order metric -benchflags '-test.run NONE -test.bench StackCopy$' go1.11..master

Unsurprisingly, this was cbafcc5 "cmd/compile,runtime: implement stack objects":

$ benchstat2 bench.log 433496615f cbafcc55e8
name          old time/op  new time/op  delta
StackCopy-12  86.6ms ± 0%  94.4ms ± 1%  +8.99%  (p=0.008 n=5+5)

/cc @randall77

I'm seeing a much larger regression here. But on a hunch, I checked, and the second half of the regression starts at c803ffc, making it a dup of #28595. cc @mknyszek as FYI.

I'm not seeing the difference reported here. Tip seems faster than 1.11.2.

name              old time/op  new time/op  delta
StackCopyPtr      93.3ms ± 2%  90.8ms ± 2%  -2.77%  (p=0.003 n=8+8)
StackCopy         68.5ms ± 1%  67.4ms ± 2%  -1.54%  (p=0.002 n=8+8)
StackCopyNoCache   118ms ± 5%   120ms ± 2%    ~     (p=0.083 n=8+8)

It would be strange for these benchmarks to be affected by the extra stack object code. None of them has a stack object, so the additional cost is just another funcdata call and an empty for loop per frame.

GC stack scanning might be more expensive for StackCopyPtr as there are a lot of intra-stack pointers, but stack copying won't see that cost.

Tip is faster than 1.11 because https://go-review.googlesource.com/c/go/+/110564 went in, which offset the other slowdown. Maybe that’s fine? Might still be worth a quick look before/after stack objects to make sure there’s no low hanging fruit.

Given the offset, removing release-blocker. This needs more investigation.

Are we still concerned about this regression?

Tip is faster than 1.11 because https://go-review.googlesource.com/c/go/+/110564 went in, which offset the other slowdown. Maybe that’s fine? Might still be worth a quick look before/after stack objects to make sure there’s no low hanging fruit.

Hello @josharian, I am doing a bit of issue gardening and wondering if we can punt this to Go1.13 and we can do investigations there. What do you think?

Punt.

Roger that, thanks @josharian!

I think given the performance offset and that there haven't been any clear problems with this during 1.12, I'm no longer worried about the underlying regression. I'm going to go ahead and close, but feel free to re-open.