Hot answers tagged performance
Some applications, when working for days can "grow up" in memory because there might be memory leaks (memory is reserved and not returned when not needed). When you have less memory (because of memory leaks) system moves information from memory to disk (swap partitions) more often, and this is probably the reason of slowing down you experience.
Actually there is a a tool named as sysbench. You can install it with sudo apt-get install sysbench To CPU benchmarking you can do like sysbench --test=cpu --cpu-max-prime=20000 run where 20000 is like max event count.
I didn't get any hardware events listed either, until after I used some. Now, even after a fresh re-boot, some are listed: doug@s15:~$ perf list hw List of pre-defined events (to be used in -e): branch-instructions OR branches [Hardware event] branch-misses [Hardware event] bus-cycles ...
You probably don't need to restart to clear the ram and swap, as you can clear both without restarting: Clearing Swap: You can turn swap off and on again to clear it (make you have enough spare memory using free -m, top or similar) using sudo swapoff -a && sudo swapon -a. If stuff is moved to swap when you have enough free memory, and you don't ...
Turns out the CPU was not cooling properly, and this wasn't reported to the OS, nor in any way did it make the system shut down. During compilation, CPUs maxed out quickly at 100C. Running sensors showed that the critical limit of the CPU was in fact 100C. After dismounting the cooler, I could see that only a small patch of thermal paste had actually ...
Only top voted, non community-wiki answers of a minimum length are eligible