Sponsored Content
Full Discussion: Cooler GPU
Special Forums Hardware Cooler GPU Post 302922387 by agentrnge on Friday 24th of October 2014 10:03:34 AM
Old 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

Tracing the GPU usage

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

GPU and CUDA

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

External GPU issue

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

CUDA GPU terminates process at random instances

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

How disabling GPU?

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

Vfio passtrough gpu, a question about hdmi

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
pset_ctl(2)							System Calls Manual						       pset_ctl(2)

NAME
pset_ctl() - processor set control SYNOPSIS
DESCRIPTION
The function provides a means to query the system processor set configuration and assignment information. The request argument specifies what information is needed for the pset processor set. The following request values are supported: Return the ID of the processor set binding for the calling thread. The pset and id arguments are ignored. Return the ID of the first locality domain contributing to the processor set pset. The id argument is ignored. Return the ID of the first processor in the processor set pset that is in the proximity of the processor specified by id. Even when the processor given by id is enabled, the return value will be -1 if none of the proximate processors contribute to the processor set pset. If the processor given by id is not enabled, -1 is returned. See mpctl(2) for details on proximate processors. Return the ID of the first processor set in the system. The pset and id arguments are ignored. Return the ID of the first processor in the processor set pset. It will return -1 if the processor set is empty. Any processors in the processor set that is in transition are ignored. The id argument is ignored. Return the ID of the next locality domain after the locality domain specified in id that contributes to the processor set pset. Typically, is called to determine the first locality domain in a processor set. is then called in a loop (until the call returns -1) to determine the IDs of the remaining locality domain in the processor set. Return the ID of the next processor in the processor set pset that is in the proximity of the processor specified by id. Typically, is called to determine the first proximate processor. is then called in a loop (until the call returns -1) to deter- mine the IDs of the remaining proximate processors. Return the ID of the next processor set in the system after pset. The id argument is ignored. Typically, is called to determine the first processor set. is then called in a loop (until the call returns -1) to determine the IDs of the remaining processor sets in the system. Return the ID of next processor in the processor set pset after the processor specified in id. Typically, is called to determine the first processor in a processor set. is then called in a loop (until the call returns -1) to determine the IDs of the remaining processors in the processor set. Return the number of locality domains that have at least one processor assigned to the processor set pset. The id argument is ignored. Return the number of processors assigned to the processor set pset that are in the proximity of the processor specified by id. Even when the processor given by id is enabled, the return value will be 0 if none of proximate processors contribute to the processor set pset. If the processor given by id is not enabled, -1 is returned. Return the current number of processor sets in the system. It will always be greater than or equal to one. The pset and id arguments are ignored. Return the number of processors assigned to the processor set pset. Any processors in the processor set that is in transition are not included. The id argument is ignored. Return number of processors contributed by the locality domain specified by id to the processor set pset. Return the ID of the processor set assigned for the processor specified in id. If the processor is not enabled or is in transition from one processor set to another, -1 is returned with an error. The pset argument is ignored. Logical Processor and Processor Core Information On systems with the Hyper-Threading (HT) feature enabled, each processor core may have more than one hyper-thread per physical processor core. When hyper-threading is enabled at the firmware level, each hyper-thread is represented to the operating system and applications as a logical processor (LCPU). Hence the basic unit of any topology information is a logical processor. However, some applications may want to get the system topology information at the physical processor core level. Returns the number of processor cores assigned to the processor set pset. Any processor cores in the processor set that are in transition are not included. The id argument is ignored. Returns the ID of the first processor core in the processor set pset. It will return -1 if the processor set is empty. Any processor cores in the processor set that is in transition are ignored. The id argument is ignored. Returns the ID of the next processor core in the processor set pset after the processor specified in id. Typically, is called to determine the first processor core in a processor set. is then called in a loop (until the call returns -1) to determine the IDs of remaining processor cores in the processor set. Returns the number of enabled processor cores assigned to the processor set pset. Any user may query the system processor set topology using the function. Use with name to see if the processor set functionality is supported by the underlying HP-UX operating system version. RETURN VALUE
returns a value based on on successful completion. Success. The value is based on the request. Failure. is set to indicate the error. ERRORS
sets to one of the following values if the corresponding condition is detected. The request is invalid. The specified processor set pset, or the processor or the locality domain specified by id is invalid. The request is and there is no other processor set after pset, or the request is and there is no other processor after id in pset, or the request is and there is no other locality domain after id in pset, or the request is and there is no other proxi- mate processor after id in pset. The request is or and the processor specified by id is not enabled. The processor set functionality is not supported by the underlying HP-UX version. EXAMPLES
Get total count and IDs of all processor sets in the system. AUTHOR
was developed by HP. SEE ALSO
psrset(1M), mpctl(2), pset_assign(2), pset_bind(2), pset_create(2), pset_destroy(2), pset_getattr(2), pset_setattr(2), sysconf(2), privi- leges(5). pset_ctl(2)
All times are GMT -4. The time now is 11:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy