10 More Discussions You Might Find Interesting
I am using HP-UX 11i v1(B11.11) servers for my work and its memory (RAM) utilization is consistenly 80% for the last one year. Though I am not facing any issues with this high memory utilization I just want to know the below queries:
1) Is it the default behavior of HP-UX systems?
2)... (20 Replies)
Discussion started by: ssk250
I have one Solaris server with high memory utilization >90%. As per checking, below is the output for memory usage.
bash-3.00# ps -efo pmem,uid,pid,ppid,pcpu,comm | sort -r
%MEM UID PID PPID %CPU COMMAND
1.7 29496 20668 1 0.0 /opt/app/iw-home/tools/java/bin/java
1.5... (1 Reply)
Discussion started by: myrpthidesis
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4. Emergency UNIX and Linux Support
Can someone please help me with a script that will help in identifying the CPU & memory usage by a process name, rather than a process id.This is to primarily analyze the consumption of resources, for performance tweaking.
G (4 Replies)
Discussion started by: ggayathri
5. Shell Programming and Scripting
Am a newbie to unix and wasnt able to write script to my requirement.
I need a shell script, which should find a process by name and kill it. For eg: let the process name be "abc". I have different processes running by this name(abc), so should kill them all.
Condition would be: if... (7 Replies)
Discussion started by: fop4658
6. Shell Programming and Scripting
I'd like to set a cron job that runs a shell script every 30 minutes or so to restart a java based service if the memory gets above 80%. Any advice on how to do this?
Thanks in advance!
- Ryan (19 Replies)
Discussion started by: prometheon123
7. Shell Programming and Scripting
I need help in preparing script to check for high cpu utilisation for java process.
I have many java process on my system which consumes high cpu so i have to monitor
it using script.
---------- Post updated 12-10-10 at 02:21 AM ---------- Previous update was 12-09-10 at... (1 Reply)
Discussion started by: coolguyamy
we upgarded our AIX from 5.3 to 6.1 and upgraded our xlc compiler from ver 6.0 to 9.0 .
After this upgrade one of our pro*C program is utilizing around 20% of the CPU. Before upgarde its using only 0.2 %.
when i try to debug using the truss command i got the below error.
$... (6 Replies)
Discussion started by: mugunthanvh
9. Shell Programming and Scripting
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
If following is the usage of cat /proc/meminfo
MemTotal: 4051304 kB
MemFree: 28544 kB
Buffers: 216848 kB
Cached: 3398628 kB
SwapCached: 0 kB
Active: 455460 kB
Inactive: 3291612 kB
HighTotal: 0 kB
HighFree: 0 kB... (5 Replies)
Discussion started by: bryanabhay
speedy_backend - the backend process for a persistent Perl interpreter
none ; this program is not meant to be called directly.
speedy, short for SpeedyCGI, is a way to run perl scripts persistently, which can make them run much more quickly.
After the script is initially run, instead of exiting, the perl interpreter is kept running inside a backend process, speedy_backend. Dur-
ing subsequent runs, this interpreter is used to handle new executions instead of starting a new perl interpreter each time. A very fast
frontend program, speedy, written in C, is executed for each request. This fast frontend then contacts the persistent Perl process, which
is usually already running, to do the work and return the results.
Each perl script runs in its own Unix process, so one perl script can't interfere with another. Command line options can also be used to
deal with programs that have memory leaks or other problems that might keep them from otherwise running persistently.
The speedy front end connects to the back end process, speedy_backend, via a Unix socket in /tmp. A queue is kept in a shared file in /tmp
that holds an entry for each process. In that queue are the pids of the perl processes waiting for connections. The frontend pulls a
process out of this queue, connects to its socket, sends over the environment and argv, and then uses this socket for stdin/stdout to the
/tmp/speedy* A unix socket used to connect to the frontend process.
This manual page was created by Niko Tyni <firstname.lastname@example.org> for Debian GNU/Linux, because the original program does not have one. It is based
on the original and more complete CGI::SpeedyCGI(3pm) manual page.
perl(1), CGI::SpeedyCGI(3pm), speedy(1)