mirrors/caddy-website
1
0
Fork 0
mirror of https://github.com/caddyserver/website.git synced 2025-04-26 06:56:15 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix a few images/links

Browse source
This commit is contained in:
Francis Lavoie 2023-12-12 10:34:47 -05:00
parent ddced518a1
commit 0287674362
No known key found for this signature in database
GPG key ID: 0F66EE1687682239
5 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

6
src/docs/markdown/profiling.md
View file

@ -400,7 +400,7 @@ Bingo. Nearly half of memory is allocated strictly for read and write buffers fr
If we instead run the `svg` or `web` commands, we'll get a visualization of the profile:
![CPU profile visualization](/resources/images/profile.png)
![CPU profile visualization](/old/resources/images/profile.png)
This is a CPU profile but similar graphs are available for other profile types.
@ -436,7 +436,7 @@ As you can see, we reduced memory allocations by about half!
Diffs can be visualized, too:
![CPU profile visualization](/resources/images/profile-diff.png)
![CPU profile visualization](/old/resources/images/profile-diff.png)
This makes it really obvious how the changes affected the performance of certain parts of the program.
@ -449,4 +449,4 @@ To really put the "pro" in "profiling", consider these resources:
- [pprof Documentation](https://github.com/google/pprof/blob/main/doc/README.md)
- [A real-world use of profiles with Caddy](https://github.com/caddyserver/caddy/pull/4978)
- [Performance on the Go wiki](https://github.com/golang/go/wiki/Performance)
- [The `net/http/pprof` package](https://pkg.go.dev/net/http/pprof)
- [The `net/http/pprof` package](https://pkg.go.dev/net/http/pprof)