From 6afb5fa48fc3d33f7973fbdfeb96fdfaad51fb5f Mon Sep 17 00:00:00 2001 From: Austin Clements Date: Thu, 9 Apr 2015 10:17:06 -0400 Subject: [PATCH] runtime: remove GoSched/GoStart trace events around GC These were appropriate for STW GC, since it interrupted the allocating Goroutine, but don't apply to concurrent GC, which runs on its own Goroutine. Forced GC is still STW, but it makes sense to attribute the GC to the goroutine that called runtime.GC(). Change-Id: If12418ca66dc7e53b8b16025af4e03adb5d9577e Reviewed-on: https://go-review.googlesource.com/8715 Reviewed-by: Dmitry Vyukov Reviewed-by: Rick Hudson --- src/runtime/mgc.go | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/runtime/mgc.go b/src/runtime/mgc.go index e8cf95e907..8ed8c57362 100644 --- a/src/runtime/mgc.go +++ b/src/runtime/mgc.go @@ -324,7 +324,6 @@ func gc(mode int) { } if trace.enabled { - traceGoSched() traceGCStart() } @@ -459,7 +458,6 @@ func gc(mode int) { if trace.enabled { traceGCDone() - traceGoStart() } // all done