Skip to content

_content/doc/gc-guide: fix typo #332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

_content/doc/gc-guide: fix typo #332

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
71df96f
_content/doc/gc-guide: fix typo
atetubou Oct 14, 2025
c9e3fa6
Update pgo.md
atetubou Oct 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _content/blog/pgo.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -350,7 +350,7 @@ Showing nodes accounting for -3.72s, 3.13% of 118.73s total
```

So `runtime.scanobject` is ultimately coming from `runtime.gcBgMarkWorker`.
The [Go GC Guide](/doc/gc-guide#Identiying_costs) tells us that `runtime.gcBgMarkWorker` is part of the garbage collector, so `runtime.scanobject` savings must be GC savings.
The [Go GC Guide](/doc/gc-guide#Identifying_costs) tells us that `runtime.gcBgMarkWorker` is part of the garbage collector, so `runtime.scanobject` savings must be GC savings.
What about `nextFreeFast` and other `runtime` functions?

```
Expand Down
2 changes: 1 addition & 1 deletion _content/doc/gc-guide.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1527,7 +1527,7 @@ <h2 id="A_note_about_virtual_memory">A note about virtual memory</h2>

<h2 id="Optimization_guide">Optimization guide</h2>

<h3 id="Identiying_costs">Identifying costs</h3>
<h3 id="Identifying_costs">Identifying costs</h3>

<p>
Before trying to optimize how your Go application interacts with the GC, it's
Expand Down