File tree 1 file changed +17
-8
lines changed
1 file changed +17
-8
lines changed Original file line number Diff line number Diff line change @@ -546,14 +546,6 @@ <h3 id="minor_library_changes">Minor changes to the library</h3>
546
546
</ dd >
547
547
</ dl > <!-- reflect -->
548
548
549
- < dl id ="runtime "> < dt > < a href ="/pkg/runtime/ "> runtime</ a > </ dt >
550
- < dd >
551
- < p > <!-- https://go.dev/issue/61015 -->
552
- TODO: < a href ="https://go.dev/issue/61015 "> https://go.dev/issue/61015</ a > : change mutex profile to scale contention by number of blocked goroutines
553
- </ p >
554
- </ dd >
555
- </ dl > <!-- runtime -->
556
-
557
549
< dl id ="runtime/metrics "> < dt > < a href ="/pkg/runtime/metrics/ "> runtime/metrics</ a > </ dt >
558
550
< dd >
559
551
< p > <!-- https://go.dev/issue/63340 -->
@@ -562,6 +554,23 @@ <h3 id="minor_library_changes">Minor changes to the library</h3>
562
554
</ dd >
563
555
</ dl > <!-- runtime/metrics -->
564
556
557
+ < dl id ="runtime/pprof "> < dt > < a href ="/pkg/runtime/pprof/ "> runtime/pprof</ a > </ dt >
558
+ < dd >
559
+ < p > <!-- https://go.dev/issue/61015 -->
560
+ Mutex profiles now scale contention by the number of goroutines blocked on the mutex.
561
+ This provides a more accurate representation of the degree to which a mutex is a bottleneck in
562
+ a Go program.
563
+ For instance, if 100 goroutines are blocked on a mutex for 10 milliseconds, a mutex profile will
564
+ now record 1 second of delay instead of 10 milliseconds of delay.
565
+ </ p >
566
+
567
+ < p > <!-- https://go.dev/issue/50891 -->
568
+ CPU profiles on Darwin platforms now contain the process's memory map, enabling the disassembly
569
+ view in the pprof tool.
570
+ </ p >
571
+ </ dd >
572
+ </ dl > <!-- runtime/pprof -->
573
+
565
574
< dl id ="runtime/trace "> < dt > < a href ="/pkg/runtime/trace/ "> runtime/trace</ a > </ dt >
566
575
< dd >
567
576
< p > <!-- https://go.dev/issue/60773 -->
You can’t perform that action at this time.
0 commit comments