Tag Info

New answers tagged


If you want just number of cores in variable: NPROC=`sysctl hw.ncpu | awk '{print $2}'`


If only load you want to know than use command top | grep "load average"


CPU steal time is (according to man proc): Stolen time, which is the time spent in other operating systems when running in a virtualized environment. If you have more than one VM on that host; or if you keep adding VM's on that host; or if you're overcommitting resources (especially CPU) you can run into this issue. I made a post about how ...


Use the repositories and don't try to install packages with the wrong architecture and dependencies. aptitude purge dia apt-get update apt-get install dia


I'm not sure what's going on, but my guess is that the individual process's %CPU column isn't telling you what you think it tells you. From top's manpage: k: %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. Let's say you're refreshing every 4 seconds. The total ...


$ sudo dmidecode |egrep "Socket Designation: Proc|((Thread|Core) Count)" Socket Designation: Proc 1 Core Count: 14 Thread Count: 28 Socket Designation: Proc 2 Core Count: 14 Thread Count: 28 Two sockets. Each socket has 14 physical cores. Each core has two threads (28/14). Total number of logical "cpus" or logical processing ...


There are a few options. My preference is the program htop which isn't generally installed by default but is available for almost all distros. It gives you the same info as top but with a MUCH richer feature set. It's great for interactively finding the problem process but it's not great for scripting. If you want to incorporate something into a ...


I had a similar problem and I did run TOP command in background and redirect it to a txt file top > top.txt & Thank you can see which process waste your CPU


It is architecture dependent - the relevant code is here (for ARM): http://lxr.free-electrons.com/source/arch/arm/kernel/setup.c#L1074 Note: for ARM, it appears that all fields should remain constant after they are computed - there is no cpu MHz (referenced by @terdon for his answer on his architecture). For example, here is the output on a Raspberry Pi: ...


Yes. For one thing, the cpu MHz field will change very often since it shows the current speed of your CPU. For example, on my system: $ for i in {1..10}; do grep -m 1 MHz /proc/cpuinfo ; done cpu MHz : 1596.000 cpu MHz : 1596.000 cpu MHz : 1596.000 cpu MHz : 1596.000 cpu MHz : 2394.000 cpu MHz : 2394.000 cpu MHz : 1596.000 cpu ...

Top 50 recent answers are included