I've been working with an HP-UX system (RP5400 Series PA-RISC server) for about a year that hosts some middleware. The middleware sits between an Oracle DB (on another box) and the client applications running on about 800 PCs. From the beginning, I've noticed that 'top' reports between 0.0% and 10% Idle during the day. Seeing that this is the first big production Unix server I've ever worked with, I believe that these Idle times are WAY too low. However, the application vendor told us that 0% idle should be OK as long as it doesn't stay there. Another support person at the application vendor, however, told me that we should be seeing between 30-60% Idle during the day! My gut feeling is that if it drops below 20% consistently, there is probably a resource issue. Here is a typical 'top' screen from our system in the middle of the day:
I've been monitoring with 'sar' as well and keeping a month's worth of 'sar' output in 15 minute intervals. A lot of what I see with 'sar' seems to reflect what I see with 'top', so I believe we are being pegged for CPU time by the user load. WIth all of this said, my base question is... what IS a reasonable Idle value/range on a Unix box? I've never actually seen this stated anywhere and I imagine it probably varies, but there should be some cushion, shouldn't there?
how can i do that in a script withough havin the script halt at the section where the top command is located. am writign a script that will send me the out put of unx commands if the load average of a machine goes beyond the recommended number.
top -n 20
i want to save this output to a file... (1 Reply)
Is there a command in SCO Unix that does the same as the top command in HPUX. The command displays the jobs using the most system resources.
Thanks You (0 Replies)
https://www.unix.com/showpost.php?p=98416&postcount=8
Referring to the post above... what is the unit that is measured in the TOP command under LOAD? (1 Reply)
Hey guys, the top format in HP-UX has the size which is the total virtual size and the res which is the resident size. What are these size and res? (1 Reply)
help! i need help with locating where a program is being run from. when i type top -i it only lists the name and minimal info, not the programs location from where it is being ran. i ask because i just used the same named executable, a.exe for all the processes and have lost the schedule detailing... (4 Replies)
Okay, I am trying to come up with a multi-platform script to report top ten CPU and memory hog processes, which will be run by our enterprise monitoring application as an auto-action item when the CPU and Memory utilization gets reported as higher than a certain threshold
I use top on other... (5 Replies)
Currently when i run top command i get the following columns .
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
In this how to remove '%WCPU' column ?
Thanks very much in advance . (6 Replies)
Hi All,
i am using the below command and once get the output and i need to keep the
first batch only.in this case how to do this one. please help me on thistop -b -n 5 >top.txt
Thanks, (3 Replies)
Discussion started by: bmk
3 Replies
LEARN ABOUT DEBIAN
plack::middleware::stacktrace
Plack::Middleware::StackTrace(3pm) User Contributed Perl Documentation Plack::Middleware::StackTrace(3pm)NAME
Plack::Middleware::StackTrace - Displays stack trace when your app dies
SYNOPSIS
enable "StackTrace";
DESCRIPTION
This middleware catches exceptions (run-time errors) happening in your application and displays nice stack trace screen. The stack trace is
also stored in the environment as a plaintext and HTML under the key "plack.stacktrace.text" and "plack.stacktrace.html" respectively, so
that middleware futher up the stack can reference it.
This middleware is enabled by default when you run plackup in the default development mode.
You're recommended to use this middleware during the development and use Plack::Middleware::HTTPExceptions in the deployment mode as a
replacement, so that all the exceptions thrown from your application still get caught and rendered as a 500 error response, rather than
crashing the web server.
Catching errors in streaming response is not supported.
CONFIGURATION
force
enable "StackTrace", force => 1;
Force display the stack trace when an error occurs within your application and the response code from your application is 500. Defaults
to off.
The use case of this option is that when your framework catches all the exceptions in the main handler and returns all failures in your
code as a normal 500 PSGI error response. In such cases, this middleware would never have a chance to display errors because it can't
tell if it's an application error or just random "eval" in your code. This option enforces the middleware to display stack trace even
if it's not the direct error thrown by the application.
no_print_errors
enable "StackTrace", no_print_errors => 1;
Skips printing the text stacktrace to console ("psgi.errors"). Defaults to 0, which means the text version of the stack trace error is
printed to the errors handle, which usually is a standard error.
AUTHOR
Tokuhiro Matsuno
Tatsuhiko Miyagawa
SEE ALSO
Devel::StackTrace::AsHTML Plack::Middleware Plack::Middleware::HTTPExceptions
perl v5.14.2 2011-07-08 Plack::Middleware::StackTrace(3pm)