I read the man page of top but it's not helpful for this question. When top tells me cpu0 is being used 50.0% by sys, cpu1 is being used 65.7% by system space, how do I break down what processes are making up that 65.7%, in system space, of the cpu? And in lsof, how do you tell which cpu a process id's threads are tied to? Tia -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kain, Becki (B.) wrote:
I read the man page of top but it's not helpful for this question. When top tells me cpu0 is being used 50.0% by sys, cpu1 is being used 65.7% by system space, how do I break down what processes are making up that 65.7%, in system space, of the cpu? And in lsof, how do you tell which cpu a process id's threads are tied to?
One, you can't Two, it doesn't matter much. "sys" merely correlates to time spent executing system-calls (i.e. kernal calls), whereas "user" correlates to the time spent executing code outside of the kernel. As far as lsof... try this: ps -ef | grep lsof once you get the PID of the lsof process(es), you can grep for them: ps -ef | grep _PID_of_lsof_goes_here -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 11 January 2008 10:33, Kain, Becki (B.) wrote:
I read the man page of top but it's not helpful for this question. When top tells me cpu0 is being used 50.0% by sys, cpu1 is being used 65.7% by system space, how do I break down what processes are making up that 65.7%, in system space, of the cpu? And in lsof, how do you tell which cpu a process id's threads are tied to?
Why do you care? I tends to shift rapidly, so programs like top that update once per second or so can't follow these changes, anyway. And I don't see how "lsof" is relevant at all. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I care because I'm trying to figure out what threads of certain processes are continuing to run at 99% of a cpu. I'd like to know what the system is considering "system space" in top's calculation of system space. I'm trying to solve a reoccurring pegging of the cpu's issue. If there is another set of commands that I should be using, please let me know Thanks -----Original Message----- From: Randall R Schulz [mailto:rschulz@sonic.net] Sent: Friday, January 11, 2008 2:51 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Top/lsof On Friday 11 January 2008 10:33, Kain, Becki (B.) wrote:
I read the man page of top but it's not helpful for this question. When top tells me cpu0 is being used 50.0% by sys, cpu1 is being used 65.7% by system space, how do I break down what processes are making up that 65.7%, in system space, of the cpu? And in lsof, how do you tell which cpu a process id's threads are tied to?
Why do you care? I tends to shift rapidly, so programs like top that update once per second or so can't follow these changes, anyway. And I don't see how "lsof" is relevant at all. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Could try this one...... while true; do clear;ps r -eo comm,pcpu,pid; sleep 1;done man ps for alot more options. HTH's On 1/11/08, Kain, Becki (B.) <bkain1@ford.com> wrote:
I care because I'm trying to figure out what threads of certain processes are continuing to run at 99% of a cpu. I'd like to know what the system is considering "system space" in top's calculation of system space.
I'm trying to solve a reoccurring pegging of the cpu's issue. If there is another set of commands that I should be using, please let me know
Thanks
-----Original Message----- From: Randall R Schulz [mailto:rschulz@sonic.net] Sent: Friday, January 11, 2008 2:51 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Top/lsof
On Friday 11 January 2008 10:33, Kain, Becki (B.) wrote:
I read the man page of top but it's not helpful for this question. When top tells me cpu0 is being used 50.0% by sys, cpu1 is being used 65.7% by system space, how do I break down what processes are making up that 65.7%, in system space, of the cpu? And in lsof, how do you tell which cpu a process id's threads are tied to?
Why do you care?
I tends to shift rapidly, so programs like top that update once per second or so can't follow these changes, anyway.
And I don't see how "lsof" is relevant at all.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kain, Becki (B.) wrote:
I care because I'm trying to figure out what threads of certain processes are continuing to run at 99% of a cpu. I'd like to know what the system is considering "system space" in top's calculation of system space.
when you run top, the default configuration is to order processes by CPU time during the latest observation time (1 second by default). and it's not system SPACE, it's the amount of TIME spent executing kernel code (as opposed to non-kernal code which is "user"
I'm trying to solve a reoccurring pegging of the cpu's issue. If there is another set of commands that I should be using, please let me know
Pegging the CPU's is not necessarily a problem. It just means that the current mix of processes is CPU bound (which is normally a GOOD thing!) Idle time only occurs when an I/O-bound process is waiting for I/O to complete)....and that's wasted CPU cycles. A pegged CPU means that the CPU is actually working to its full potential. The only time it's an issue is if the computer is used interactively (i.e. not a compute server, such as running FEA or CFD jobs) ***AND*** the interactive interface is too sluggish. A much more significant problem is one that we had when I was at KMart headquarters about 10 years ago. New distribution-center inventory/management system...on an Informix Database, and 4-CPU HP 9000 series machine---Running VERY slowly. Idle time was about 95%. Against my advice, management threw in 4 MORE CPUS...now we had an 8 CPU box running at 97.5% idle.... The problem turned out to be that the database part of the application was wrong. This installation was at a warehouse over 10x larger than any previous installaitions of the software -- And entire tables of the database (30,000+ rows typical) were being put under exclusive lock (no READS allowed!) because the original programmer was lazy. Once this was discovered, the software was debugged, replacing table locks with code locking individual rows. Once this was done, CPU usage WENT UP... which was a GOOD THING(tm)! *AND* we were able to reduce the number of CPUs to only two (and that was just for redundancy... CPU usage was still less than 1/N where N is the number of installed CPUs.
Thanks
-----Original Message----- From: Randall R Schulz [mailto:rschulz@sonic.net] Sent: Friday, January 11, 2008 2:51 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Top/lsof
On Friday 11 January 2008 10:33, Kain, Becki (B.) wrote:
I read the man page of top but it's not helpful for this question. When top tells me cpu0 is being used 50.0% by sys, cpu1 is being used 65.7% by system space, how do I break down what processes are making up that 65.7%, in system space, of the cpu? And in lsof, how do you tell which cpu a process id's threads are tied to?
Why do you care?
I tends to shift rapidly, so programs like top that update once per second or so can't follow these changes, anyway.
And I don't see how "lsof" is relevant at all.
Randall Schulz
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 11 January 2008 12:35, Kain, Becki (B.) wrote:
I care because I'm trying to figure out what threads of certain processes are continuing to run at 99% of a cpu. I'd like to know what the system is considering "system space" in top's calculation of system space.
I'm trying to solve a reoccurring pegging of the cpu's issue. If there is another set of commands that I should be using, please let me know
None of that has anything to do with which CPU is executing any given thread at any particular moment.
Thanks
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
okay, I'm trying to solve why certain processes keep pegging cpu's and not letting them go. What do you suggest I use to track this down? Thanks in advance -----Original Message----- From: Randall R Schulz [mailto:rschulz@sonic.net] Sent: Friday, January 11, 2008 5:23 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Top/lsof On Friday 11 January 2008 12:35, Kain, Becki (B.) wrote:
I care because I'm trying to figure out what threads of certain processes are continuing to run at 99% of a cpu. I'd like to know what the system is considering "system space" in top's calculation of system space.
I'm trying to solve a reoccurring pegging of the cpu's issue. If there is another set of commands that I should be using, please let me know
None of that has anything to do with which CPU is executing any given thread at any particular moment.
Thanks
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 14 January 2008 07:14, Kain, Becki (B.) wrote:
okay, I'm trying to solve why certain processes keep pegging cpu's and not letting them go. What do you suggest I use to track this down?
Well, for starters you have to identify the processes in question and find out what they do or are supposed to do. It's true that most of the routine monitoring application (top, e.g.) are somewhat crude. If a program just pegs the CPU for an extended period of time, then you can clearly see that in top or one of its brethren. But if a program makes excessive but sporadic use of the CPU, it won't help. And if the CPU is not tied to a process (excessive interrupts, e.g.), then it won't cause any process to move up on a top listing 'cause the CPU utilization is not accounted to any process. The most sophisticated program you have for monitoring your system is KDE System Guard. It can record and display a lot of information both locally and remotely. It can show a tabular display such as that of (or, more aptly, like "qps") and it can plot values graphically over time.
Thanks in advance
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kain, Becki (B.) wrote:
okay, I'm trying to solve why certain processes keep pegging cpu's and not letting them go. What do you suggest I use to track this down?
The source code. But...as I said earlier, that's not necessarily a bad thing, IF the process is actually getting work done...then it might actually be a good thing. Have you investigated the use of nice(1) and renice(1) ????
Thanks in advance
-----Original Message----- From: Randall R Schulz [mailto:rschulz@sonic.net] Sent: Friday, January 11, 2008 5:23 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Top/lsof
On Friday 11 January 2008 12:35, Kain, Becki (B.) wrote:
I care because I'm trying to figure out what threads of certain processes are continuing to run at 99% of a cpu. I'd like to know what the system is considering "system space" in top's calculation of system space.
I'm trying to solve a reoccurring pegging of the cpu's issue. If there is another set of commands that I should be using, please let me know
None of that has anything to do with which CPU is executing any given thread at any particular moment.
Thanks
Randall Schulz
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Aaron Kulkis -
Dave Crouse -
Kain, Becki (B.) -
Randall R Schulz