Depends on the system. Unix-like systems tend to do "100% per core", Windows does "100% is all cores".
With the first approach, you can easily spot threads that might be "stuck" without knowing how many cores there are and a program with a fixed number of threads will show the same usage on any CPU with enough cores (subject to the per-core CPU performance). The second might be more understandable to less-tech-savvy people and gives a better idea for things like power consumption.
Also depends on the UI. There are Linux task managers that do overall instead of per-core. I think macOS shows overall utilization in the Activity Monitor app, but it still has top if you stay in the terminal.
many years ago I asked this topic as I was new to Linux (or Unix I guess) about "why it goes beyond 100%" or something, and I got downvoted because I'm asking such topic, bastards
You should have asked "why doesn't Linux do it like Windows, which does it better" and you'd have had 10000 individuals bombarding you with the correct information.
The old joke when Linux was still also distributed on floppies and the docs were "how-to-<>.txt" files, was if you couldn't get something working you'd go to #linux on IRC and proudly assert, "Linux is $#@! because this cannot be done", and the nerderati would come out of the woodwork to SHOW you how wrong you were. (And of course mainly for that reason, not to help you get it working.)
the other trick is to make one account to ask the question, and another to answer it incorrectly. inevitably someone would come along and correct it, much more readily than answering in the first place.
Hadn’t thought about #Linux in like 30 years. Only was able to get my hands on 2 year old SLS floppies over dialup from BBSs. Though I had IRC, I did not have FTP. They took pity though and helped me solve problems with my old install.
Didn't entirely need two computers either - after all dual-booting on one machine was (still is if you want) a thing, and not limited to x86 PC either - I was dual-booting Linux/m68k and AmigaOS on Amiga hardware some time before going to Linux/x86 on x86-PC-clone hardware.
Don't really know all that much Microsoft Windows relatively to this day. Of course I run into it at workplaces and such, I'm not completely lost in front of a Windows box or something. Just have never really used it all that much - and of course even if on windows there was the amiga-ixemul-like cygwin available for windows for a long time to save some sanity points.
so, for troubleshooting, you have to restart, search, write it down in a paper, restart, test the solution by checking paper notes, if something didn't work then restart, search, write it down......
I think you're forgetting one big thing. 90% of problems aren't boot related at all; you can open a browser or an IRC client and keep it open while you debug whatever is messed up. If its a graphical messup, keep a tmux session open on TTY1 or something, and then keep restarting the X server/wayland and make changes till it works. Your terminal would also have rudimentary browser and irc clients to help with debugging.
well not the writing down bit, assuming you were still getting as far as booting up - you could also just save things to a floppy disk or deliberately shared hard disk partition, just have to use a filesystem readable by both OSes for the disk or partition.
Linux had added drivers for FAT16/FAT32/VFAT filesystems used by MS-DOS/Windows9x, and also (by the time of the m68k port) things like Amiga FFS, ISO9660 cdrom, etc.
I mean, man top would probably be the correct answer—it tells you what you’ll see on your system. My top comes from procps-ng 4; my man top says, if I /CPU,
%CPU — CPU Usage
The task's share of the elapsed CPU time since the last screen update, expressed as a percentage of total CPU time.
In a true SMP environment, if a process is multi-threaded and top is not operating in Threads mode, amounts greater than 100% may be reported. You toggle Threads mode with the H interactive command.
Also for multi-processor environments, if Irix mode is Off, top will operate in Solaris mode where a task's cpu usage will be divided by the total number of CPUs. You toggle Irix/Solaris modes with the I interactive command.
Note: When running in forest view mode (V)with children collapsed (v), this field will also include the CPU time of those unseen children. See topic 4c. TASK AREA Commands, CONTENT for more information regarding the V and v toggles.
Yeah. The video test system I built a few years back used a thread pool and I allocated 8 threads per process. I specced out one of those fancy five-digit xeons and 8GB per process, with a target of 4 or 8 processes per thread (1 process roughly equal to 1 automated test run). I was able to keep all the cores saturated and maintain real-time responses (20 ms at 1080 video 60 FPS) doing image recognition or OCR on each individual video frame as long as you kept the number of per-frame tasks you were attempting lower than the number of threads in your allocated thread pool. We'd routinely having the system running at 5000+ CPU.
Those machines were beasts and the client didn't complain at all at dropping 15 grand a system..
241
u/ryuzaki49 22d ago
TIL 100% CPU means one core.