I really wish I could respond with a “
” instead of a heart. That one had me laughing!
1 Like
Update:
<masochist>
I tried opening a YouTube video. . . .
Results:
Load factor of almost six!
</masochist>
1 Like
And while we’re on that subject. . . .
The Reddit coffee page pegged all four processors, ran the load factor to well over six, slammed memory, and used up half of my swap.
Sheesh! Are they running a crypto-mining script in the background? The number of chromium processes that it spawned looked like the first chapter of Understanding the Linux Kernel[1] by O’Reilly.
==================== Footnotes ====================
- If you really want a quick course in the hoops that the kernel writers have to go through, that’s the book for you. The first chapter goes into the details of what happens when the kernel boots, from power-on to the point where it switches from kernel mode to user mode.
It made my head spin. It took a couple of pages just to describe all the memory structures that had to be created just to switch from real mode to protected mode - and then protected mode has to do itself like a pretzel to move all those structures out of the real (lowmem) memory space up into protected kernel memory!
Of course, when all this is set up, the benefit is that process swapping becomes a simple matter of juggling a few pointers and paging is as simple as loading/unloading a file into a prepared memory slot and linking (or unlinking), a few pointers. It’s still not something for the faint-of-heart, but it’s a lot less complex than you might think process swapping would be.
1 Like
Too much Raspberry and not enough caffeine in that coffee.
1 Like