- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- how to analzye collect data.
Operating System - Tru64 Unix
1752415
Members
6381
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2003 07:46 PM
тАО11-23-2003 07:46 PM
how to analzye collect data.
Hi
I want to analyze the system performance problem by collect tools.
I find CPU is very busy, but memory and disk I/O isn't busy.
The SYSC is 32927 and CS is 12670 , maybe this is root cause of the poor system performance.
but i don't know how to comfirm why and which process cause SYSC and CS.
very thanks
The collect data about CPU.
# CPU SUMMARY
# USER SYS IDLE WAIT INTR SYSC CS RUNQ AVG5 AVG30 AVG60 FORK VFORK
49 23 29 0 1193 32927 12670 3 3.94 3.90 3.68 41.70 0.00
# SINGLE CPU STATISTICS
# CPU USER SYS IDLE WAIT
0 46 23 31 0
1 49 24 27 0
2 52 21 28 0
3 49 23 29 0
I want to analyze the system performance problem by collect tools.
I find CPU is very busy, but memory and disk I/O isn't busy.
The SYSC is 32927 and CS is 12670 , maybe this is root cause of the poor system performance.
but i don't know how to comfirm why and which process cause SYSC and CS.
very thanks
The collect data about CPU.
# CPU SUMMARY
# USER SYS IDLE WAIT INTR SYSC CS RUNQ AVG5 AVG30 AVG60 FORK VFORK
49 23 29 0 1193 32927 12670 3 3.94 3.90 3.68 41.70 0.00
# SINGLE CPU STATISTICS
# CPU USER SYS IDLE WAIT
0 46 23 31 0
1 49 24 27 0
2 52 21 28 0
3 49 23 29 0
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2003 10:48 PM
тАО11-23-2003 10:48 PM
Re: how to analzye collect data.
Jack,
The number of System Calls and ContextSwitches are systemwide and I can assure you that I have seen already much higher values.
Runqueue and load-averages are perfect for a 4 CPU system.
You didn't mention the network. Check for saturated networks, collisions
Do you have objective figures to prove the poor performance ?
Joris
The number of System Calls and ContextSwitches are systemwide and I can assure you that I have seen already much higher values.
Runqueue and load-averages are perfect for a 4 CPU system.
You didn't mention the network. Check for saturated networks, collisions
Do you have objective figures to prove the poor performance ?
Joris
To err is human, but to really faul things up requires a computer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2003 12:32 AM
тАО11-24-2003 12:32 AM
Re: how to analzye collect data.
I agree with Joris. At first glance this all appears fine. Is there a reason to worry, or is the system simply doing it's job? This biggest indication of problem in the information provided it the high system time. You may want to try to understand what the system is doing. For that you could use the standard kprof tool, but I'd recommend downloading DCPI from the Tru64 sites.
Hein.
Hein.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP