10-24-2014
Newer kernels include more support for CPU throttling, C-states. Probably stepping down the CPU when it can. What kind of load is the system usually under? Honestly even if your CPU is pegged 100% 24/7 you shouldnt be in 75-80C. Thats way too hot. 60C is where you want to be for a non-overclocked CPU even at 100% duty cycle. 30-45 for idle or normal use.
There is an entry in the kernel cpu config to enable or disable turbo speeds. ( not overclocking specifically) Maybe the old config happened to have that enabled, and the new one is disabled by default?
Not that you can compare to values pre-upgrade, but two things to look at that might be of use is to check the physical power usage of the box with a power-meter inline from the socket to the PSU. They can be had for $20-30. Again, not all that usefull without having "before" values to compare too. But more info on your system is always good to have. Second thing to look at is install "turbostat". It will show you the clock-rates and precentage of time each core is spending in various C states ( full power through idle/power-save modes). There are a handful of other tools that show the same info. Thats just the one I happened to use recently.
This User Gave Thanks to agentrnge For This Post:
6 More Discussions You Might Find Interesting
1. Solaris
Hello,
Can give me some tips to trace the GPU usage on a solaris8 update7 box?
I try to understand why a Cadcam app is so slow on my Solaris box compared to a win$ box. I guess it comes from the poor graphic card I have but i would like to emphasize it.
My bench is 150sec long on a Solaris... (0 Replies)
Discussion started by: solea
0 Replies
2. UNIX for Advanced & Expert Users
Hi ,
i want begin programming using CUDA
which enviroment can i get .I don't have desktop to buy GPU graphics card.
what should to do to get CUDA enviroment.
i'm thinking to buy desktop has this card or laptop (1 Reply)
Discussion started by: Scotch
1 Replies
3. Hardware
Dear all,
I set up a external Gforce GPU using the PE4H (Pcie passive adapter) from HWTOOLS.NET.
I'm able to add and remove the device doing
and
The point is the kernel does not initialized the device correctly.
Here is what dmesg gives after the scan:
lspci -t gives
and lspci... (2 Replies)
Discussion started by: aihake
2 Replies
4. Hardware
I am trying to start troubleshooting an error on a virtual server that uses the ubuntu 14.04 OS. Basically what happens (seeming random) is that the GPU stops processing and terminates. What Imean by seeming random is that for 3 runs there is no error then on run 4 the error appears. It has... (2 Replies)
Discussion started by: cmccabe
2 Replies
5. Hardware
Hi All
I'm find out a way to disable the DGD: AMD Radeon HD 7470M on my Ubutu 16.04.2 LTS because radeon open source module is not capable to support this GPU and consequence the boot is very slow.
I have tried serveral way with pci-stub.ids in the grub menu but not work.
In general how... (11 Replies)
Discussion started by: _Fabio_79
11 Replies
6. Linux
The situation
videocard n°1 Nvidia Ge-force(used on host linux)
videocard n°2 Ati radeon(used on guest windows 7)
host is Slackware 14.2,kernel 4.18.15
I had set vfio to pass a ati card to windows7 guest
Configure /etc/modprobe.d/vfio.conf
options vfio-pci... (1 Reply)
Discussion started by: Linusolaradm1
1 Replies
LEARN ABOUT OSF1
processor_sets
processor_sets(4) Kernel Interfaces Manual processor_sets(4)
NAME
processor_sets - Collections of processors
DESCRIPTION
A processor set is a collection of processors. When a processor set is first created, it does not contain any processors. You can add
processors to a processor set, remove processors from a processor set, and also destroy the processor set. In addition, you can assign
specific processes to a processor set.
When the system is booted, all its processors are assigned to the default processor set. Each processor in a system can be a member of
only one processor set at one time.
In addition, when you create a process, it is assigned to a processor set. Unless you indicate a specific processor set, a process is
assigned to the default processor set. A process can execute only on an processor that is included in the processor set to which the
process is assigned. If you assign a process to an empty processor set, it will not execute until a processor is assigned to the processor
set or until the process is assigned to another processor set.
Use the pset_create command or the create_pset function to create a processor set. When you first create a processor set, it does not con-
tain any processors.
Use the pset_assign_cpu command or the assign_cpu_to_pset function to assign processors to a specific processor set. When you assign a
processor to a specific processor set, the processor is removed from its current processor set.
Use the pset_destroy command or the destroy_pset function to destroy a processor set. Processors that belong to a destroyed processor set
are assigned to the default processor set.
Use the pset_assign_pid command or the assign_pid_to_pset function to assign a process to a specific processor set. In addition, you can
request that a process has exclusive access to a processor set. If a process has exclusive access to a processor set, no other process is
able to use that processor set. If a process has exclusive access to a processor set, that access will be cleared automatically when the
process exits. Note that if a process is already assigned to a processor set, a request for exclusive access to that processor set will be
denied.
Use the pset_info command to display the status of each processor set on the system as well as the status of each processor.
You must be root to create and destroy processor sets and to assign a processor to a processor set. Processor set creation and destruction
and processor assignments to processor sets are logged in the /var/adm/wtmp file.
FILES
/var/adm/wtmp
RELATED INFORMATION
Commands: pset_create(1), pset_destroy(1), pset_info(1), pset_assign_pid(1), pset_assign_cpu(1), runon(1), psrinfo(1), psradm(8)
Functions: assign_pid_to_pset(3), assign_cpu_to_pset(3), create_pset(3), destroy_pset(3) delim off
processor_sets(4)