3 ms·
Are you referring to the kmem_cache_alloc calls in the profile? If so, that's all in kernel space and there's nothing I can do about it. https://share.firefox.
by 201984 2y ago
Are you referring to the kmem_cache_alloc calls in the profile? If so, that's all in kernel space and there's nothing I can do about it.
https://share.firefox.dev/3XT9L7P https://share.firefox.dev/3XT9L7P
- jeffbee 2y agoNo, see how your profiles have `lookup_fast` at the leaves? Mine has `__lookup_slow` and it is slow indeed.
- 201984 2y agoI just saw your edit. You have WAY more stuff under your home directory than I do. I only have ~2.5M inodes on both my laptop drives combined. The difference in the buff/cache output of `free` before and after running `dut` is only 1 GB for me. Also, TIL about that kernel parameter, thanks!
- jeffbee 2y agoYeah I have a TB of bazel outputs in my cache directory. Unfortunately automatically deleting old bazel outputs is beyond the frontier of computer science and has been pushed out to future releases for 6 years and still going: https://github.com/bazelbuild/bazel/issues/5139 https://github.com/bazelbuild/bazel/issues/5139