Explore >> Select a destination
|
You are here 
|
venam.net | ||
| | | | |
peteris.rocks
|
|
| | | | | Explanation of everything you can see in htop/top on Linux | |
| | | | |
nikgrozev.com
|
|
| | | | | Most software engineers know about operating system (OS) level processes and threads. They are taught in all university OS courses. However, newer concepts p... | |
| | | | |
thorstenball.com
|
|
| | | | | [AI summary] The article explains how Unicorn, a web server, leverages Unix system calls and concepts like fork, pipe, and signal handling to efficiently manage web requests. It highlights features such as hot reloading, zero downtime deployments, and worker process scaling using signals. The author emphasizes that these capabilities are not magic but a result of understanding and utilizing Unix's low-level mechanisms. The article also discusses the importance of knowing system-level details for debugging, architectural decisions, and deeper understanding of how software operates on the underlying system. | |
| | | | |
mazzo.li
|
|
| | | Let's say that you have a program which relies on huge pages for performance. I couldn't find a resource fully explaining how to allocate huge pages at runtime, making sure that the huge page allocation was successful, so here it is. | ||
