50 Shades of System Calls

Brilliant. (I note that the founder of this product co-authored the Winpcap packet capture library on Windows back in the day, and therefore made Ethereal/Wireshark on Windows possible.)

Nice work! I sometimes use strace&#x2F;ltrace and this program would certainly be nice addition my toolbox!<p>One thing I find useful sometimes for debugging purposes is to actually see the contents of each system call. Do I get to see that when I click on individual boxes here?

It is fun to observe that everyone might be busy tinkering with mentioned features instead of commenting.

This guy talks of &#x27;latencies&#x27; when he really means &#x27;durations&#x27;.<p>The latency is the time between stimulation and response, not the overall duration.<p>In this case the latency of a syscall would be the time between a user program performing a syscall and it starting to operate, <i>not</i> the entire time taken.

Sysdig makes me giddy like dtrace used to.<p>I also sometimes feel a bit ... challenged ... by translating the questions I have (e.g. why did this arbitrary program start using a lot of memory and then OOM) into actual sysdig chisel invocations, but I&#x27;m learning slowly but surely. This command line spectrogram looks like a really nice addition to the existing toolset!

Wow, that looks really impressive.<p>I wonder if the visual representation should somehow emphasize the slow calls more. The example on the page immediately draws the attention to that cluster of many fast calls, when the interesting part for optimizations is likely in the 100ms and slower range.

Sysdig is absolutely incredible software, but when are you going to work on getting it upstream in the Linux kernel? That will massively lower the barrier to entry and make sysdig &quot;win&quot; so to speak.