In this blog, we’ll see practically how we can build a simple sampling-based continuous profiler, leveraging frame pointers.

wGrep provides a grep-like to search for text patterns on web pages recursively.

Similarly, wFind provides a find-like way to recursively search for web locations across a hyerarchy.

As of the current support, the assumption is that points in the hyerarchy are linked with hypertext links inside web pages.

The first episode of my new blog series is live! This series dives into frame pointers and their critical role in building a CPU profiler.

This episode will explore the fundamentals of a program's execution environment. By the end, you'll understand how frame pointers become essential for stack walking, a key technique in profiling.

The second episode will tackle the practical side by diving into coding a simple sampling-based profiler with the Linux kernel assistance.

A blog about how I improved consistency and performance in a Go crawler.

Thank you, very exhaustive and interesting. A note: the link to bftrace script is broken.

I’m happy to hear that :-)

Thank you!

Thank you all for this. Scheduling on GPUs is a topic in the dark for me, to be discovered

GPU "threads" aren't exactly CPU threads, and GPU "cores" aren't really CPU cores. It's better to think of threads as SIMD instructions and cores as ALUs.

GPU execution order is typically either "immediate mode" or "tile mode", where tiles are more common on mobile GPUs, but Nvidia has also used them.

https://www.realworldtech.com/tile-based-rasterization-nvidi...

thank you for the details!

Thank you, it seems very interesting. I leave here links also for other people. - https://docs.sel4.systems/projects/sel4/documentation.html

Yes, you're right. I preferred to not cover too much topics on the same blog, but that's a good idea as other people said here. Thank you.