Sponsored Content
Top Forums UNIX for Dummies Questions & Answers I have a 12 core Linux cpu but the load is really high on this box, hovering around 50. Post 302911385 by rbatte1 on Thursday 31st of July 2014 12:22:59 PM
Old 07-31-2014
Welcome Moon1234,

What server do you have? When you are saying "hovering around 50", do you mean:-
  • 50% CPU busy, 00% IO wait & 50% idle
  • 00% CPU busy, 50% IO wait & 50% idle
  • 50% CPU busy, 50% IO wait & 00% idle
  • Is it swapping/paging?
Depending what situation and hardware you've got depends on how we can respond. Maybe your application just has very poor logic, or you are really crunching vast amounts of data. From your single statement, we can't really tell.

What type of processing is actually being done? On some servers, I'd be very happy at 50%, others I would be concerned I had a looping process.



Regards,
Robin
 

9 More Discussions You Might Find Interesting

1. AIX

Application high CPU load

after a long period of running, the network application's CPU load in our syst em increase slowly, the failed at the end. we use "truss" tool to trace the process, found that it processes something like "semop" ,"semctl","thread_waitlock","kread" kernel call . The trace log file looks like the... (0 Replies)
Discussion started by: Frank2004
0 Replies

2. UNIX for Advanced & Expert Users

Sun: High kernel usage & very high load averages

Hi, I am seeing very high kernel usage and very high load averages on my system (Although we are not loading much data to our database). Here is the output of top...does anyone know what i should be looking at? Thanks, Lorraine last pid: 13144; load averages: 22.32, 19.81, 16.78 ... (4 Replies)
Discussion started by: lorrainenineill
4 Replies

3. HP-UX

HIgh Load

Hi All. In my production server the load is very high. normally it used to be less than 1,but now it is more than 5. I am new to unix all together. I want to know what is the reason behind high load. and if it is high what is the impact? (4 Replies)
Discussion started by: jyoti
4 Replies

4. Red Hat

High cpu load average

Hi Buddies, Thanx for reading my first post... After googling a lot and searching so many forums I am feeling down a bit... Please don't mind my ignorence, and my grammer ... :) My server is running RHEL 2.6.9-5.EL. The cpu load is going higher than roof, almost 100 sometimes. I am... (2 Replies)
Discussion started by: squid04
2 Replies

5. Shell Programming and Scripting

script to generate core if cpu is high

Hi guys, I need a script that will generate a core of a process when the process uses high cpu for a sustained period? So for example if a process is using greater than 80% cpu for more than 30 minutes do "gcore /var/tmp/process.core pid" (1 Reply)
Discussion started by: borderblaster
1 Replies

6. UNIX for Advanced & Expert Users

What's a high load for my system?

I'm not sure if this belong in dummies or advanced so I made my best guess. Go easy on me if I get it wrong. I'm trying to determine what a high load for my system is. I run a php/mysql web server with a dedicated host. The host has a Intel Xeon 3110 (Dual Core) processor. Our load seems to... (5 Replies)
Discussion started by: vanguard
5 Replies

7. Red Hat

apache high cpu load on high traffic

i have a Intel Quad Core Xeon X3440 (4 x 2.53GHz, 8MB Cache, Hyper Threaded) with 16gig and 1tb harddrive with a 1gb port and my apache is causing my cpu to go up to 100% on all four cores heres my http.config <IfModule prefork.c> StartServers 10 MinSpareServers 10 MaxSpareServers 15... (4 Replies)
Discussion started by: awww
4 Replies

8. Shell Programming and Scripting

what would a script include to find CPU's %system time high and user time high?

Hi , I am trying to :wall: my head while scripting ..I am really new to this stuff , never did it before :( . how to find cpu's system high time and user time high in a script?? thanks , help would be appreciated ! :) (9 Replies)
Discussion started by: sushwey
9 Replies

9. Shell Programming and Scripting

Restart debian server if one specific process has more than 10 seconds have high cpu load

Hi, could someone give me an example for a debian server script? I need to check a process if the process has a high cpu load (top). If yes the whole server needs to reboot. Thats it, nothing more. ;) Hope someone could help me. Regards woisch (2 Replies)
Discussion started by: woisch
2 Replies
pthread_mutexattr_getspin_np(3T)										  pthread_mutexattr_getspin_np(3T)

NAME
pthread_mutexattr_getspin_np(), pthread_mutexattr_setspin_np(), pthread_mutex_getyieldfreq_np(), pthread_mutex_setyieldfreq_np(), pthread_mutexattr_disable_handoff_np(), pthread_mutex_disable_handoff_np() - get and set mutex spin and yield frequency attributes; disable mutex-specific or process-wide mutex handoff mode SYNOPSIS
PARAMETERS
attr Pointer to the mutex attributes object whose attributes are to be set/retrieved. spin This parameter either specifies the new value of the spin attribute (set function) or points to the memory location where the spin attribute of attr is to be returned (get function). yield This parameter either specifies the new value of the yield frequency process-wide attribute (set function) or points to the mem- ory location where the yield frequency process-wide attribute is to be returned (get function). DESCRIPTION
These attributes are used to tune the mutex locking behavior for optimized application performance on multiprocessor systems. For and the attributes object attr must have previously been initialized with the function before these functions are called. Attribute: spin Mutexes can be initialized with a spin value which is used by for busy-wait iterations on the mutex lock. It is effective only on multi- processor systems. It is ignored on uniprocessor systems. For bound threads, the procedure to block on a busy mutex is quite costly. On a multiprocessor system, the thread holding the mutex may be a few instruction cycles away from releasing it. By performing a brief busy-wait before actually blocking, the lock path can avoid a great deal of overhead in these situations. For many applications, these situations are not rare. Consider a mutex used to protect a short sequence of code (e.g., to increment a counter). The mutex is held only for a few instruction cycles (plus the function call overhead for The ability to set the spin attribute allows the application writer to adjust the busy-wait to suit the duration of the common-case criti- cal section protected by each mutex. The legal values for the spin attribute are: The function will busy-wait on the mutex lock for the specified number of iterations before blocking the thread, unless the lock is acquired sooner. Larger spin values would be appropriate for mutexes associated with longer critical sections. Inhibits blocking on the mutex lock altogether. The function will busy-wait on the mutex lock until it is acquired. Uses a built-in default value for the number of busy-wait iterations. Attribute: yield Note that the yield attribute is not a per-mutex attribute, but is process-wide. That is, it affects the behavior of all mutexes. The yield attribute specifies, for the busy-wait, how frequently the processor should be yielded (via allowing other threads to execute. When the number of threads exceeds the number of processors in a system, a busy-wait on a mutex can sometimes have an adverse effect. The busy-wait itself can prevent the thread holding the lock from completing the associated critical section of code. By yielding the proces- sor on occasion, the thread attempting the lock may allow the thread holding the lock to reach the point at which it can release the lock. However, it still avoids the costly path to block on the mutex. The legal values for the yield attribute are: The busy-wait loop in will yield the processor after each specified number of iterations of the spin loop (where the total number of iterations is con- trolled by the per-mutex spin attribute). Inhibits yielding in the mutex lock altogether. Uses a built-in default value for the frequency of yields in the busy-wait loop. The and functions are provided for binary compatibility purposes only. They will not have any noticeable effect on mutexes. RETURN VALUE
and return the following values: Successful completion. Failure. The returned value is an error number defined in the ERRORS section. (The variable is not set). ERRORS
If an error is detected, and return one of the following error numbers. The value specified by attr, spin, or yield is invalid. was called after the process became multithreaded. WARNINGS
The settings of the spin and yield attributes can, as well as improve application performance, easily lead to degraded performance. The CPU consumption of the application may be increased. Settings which work well for a small number of threads may do poorly for larger num- bers of threads. The optimal settings will vary depending upon hardware and operating system configuration. Minor changes in the applica- tion itself may require retuning of these attributes. The programmer must analyze performance carefully to obtain an understanding of mutex contention within the application. Then, experiment with different attribute values, evaluating how mutex contention is affected, response time, and CPU consumption. AUTHOR
and were developed by HP. SEE ALSO
pthread_create(3T), pthread_mutex_init(3T), pthread_mutexattr_init(3T), rtsched(2) STANDARDS CONFORMANCE
Pthread Library pthread_mutexattr_getspin_np(3T)
All times are GMT -4. The time now is 10:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy