|
You are here |
www.markwrobel.dk | ||
| | | | |
www.thedigitalcatonline.com
|
|
| | | | | A blog featuring in-depth posts about Python, Scala, TDD, devops, security and all things development | |
| | | | |
blog.maxgio.me
|
|
| | | | | Profiling the CPU allows us to analyze the program's performance, identify bottlenecks, and optimize its efficiency. Have you ever wondered what happens behind the scenes when you run a program and how to account for CPU time for the actual program functions? And even more, how to write such a tool to profile the program? Even though great open-source projects provide continuous profiling with vast support for compiled, JITed, and interpreted, languages, with or without debug info, with or without frame ... | |
| | | | |
manybutfinite.com
|
|
| | | | | Earlier we've explored the anatomy of a program in memory, the landscape of how our programs run in a computer. Now we turn to the call stack, the work horse in most programming languages and virtual | |
| | | | |
hjr265.me
|
|
| | | Last night, I encountered a strange issue setting up Steam Link on a Raspberry Pi running Retro Pie. Here is my attempt at a proper description of what I was seeing. After installing Steam Link using Retro Pie's package manager and rebooting the Raspberry Pi, I could see "Ports" show up on the Emulation Station. Inside was "Steam Link". I could start Steam Link just fine, have it test my network, and then pair it with Steam running on my gaming virtual machine. | ||