Skip to content

Commit 7dd1b17

Browse files
committed
tweak conclusion, add paragraph about the screenshot
1 parent 0b6dcca commit 7dd1b17

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

posts/2025/02/allocation_sampling.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -243,11 +243,13 @@ All benchmarks executed on:
243243

244244
### Example
245245

246-
<img src="/images/2025_02_allocation_sampling_images/allocation_sampling_call_tree.png">
246+
We have also modified [vmprof-firefox-converter](https://github.com/Cskorpion/vmprof-firefox-converter/tree/allocation_sampling) to show the allocation samples in the Firefor Profiler UI. With the techniques from this post, the output looks like this:
247247

248+
<img src="/images/2025_02_allocation_sampling_images/allocation_sampling_call_tree.png">
248249

250+
While this view is interesting, it would be even better if we could also see what types of objects are being allocated in these functions. We will take about how to do this in a future blog post.
249251

250252

251253
## Conclusion
252254

253-
In this blog post we introduced allocation sampling for PyPy by going through the technical aspects and the corresponding overhead. In a future blog post, we are going to dive into the actual usage of allocation sampling with VMProf, and show an example case study. That will be accompanied by some new improvements and additional features, like extracting the type and (hopefully) size of an object that triggered a sample.
255+
In this blog post we introduced allocation sampling for PyPy by going through the technical aspects and the corresponding overhead. In a future blog post, we are going to dive into the actual usage of allocation sampling with VMProf, and show an example case study. That will be accompanied by some new improvements and additional features, like extracting the type of an object that triggered a sample.

0 commit comments

Comments
 (0)