Hi gophers,
We have a web service running with high minor page fault and I'm trying to
understand why. I start by using linux perf:
```bash
sudo perf record -e minor-faults -c 1 -C 0-2 -ag -- sleep 15
sudo perf script > perf.out
```
and in the output file perf.out, I found many strange trace records:
```
tsproducer-prod 390772 [002] 2661398.756621: 1 minor-faults:
ea8a10 memcpy+0x24 (/usr/local/bin/tsproducer-prod)
```
and they are the majority of all records.
these records surprise me that it contains no stack trace between, seem
like it's calling memcpy from nowhere, and i can not understand how this
could happen base one my knowledge. I would expect something like
"runtime.goexit.abi0" or "runtime.asmcgocall.abi0" before "memcpy".
By the way, this code is compiled using go 1.22.2
I should attach a flame graph generated base on perf.out.
please advise me on how to further understand this, maybe I miss some doc?
Thanks a lot,
Zhao Weng
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/2cc16e0f-176b-4f33-8798-bba239a4ec1cn%40googlegroups.com.
