04-08-2014
The compile jobs are periodic & run by us.
Same job used to complete in ~3 hrs earlier (a week back) which are now taking ~20 hrs.
No configuration change has happened on the system.
Don't see anything else hogging the system.
Hence wondering what's slowing it down.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I've got some CPU bottleneck on a HP-UX 11 server : i didn't
understand it until i discover i've got an unusual high percentage
of NICE% CPU regarding my DBRMS process (Sybase 12.x).
How do i have to understand it and how to resolve it ?
Thx. (0 Replies)
Discussion started by: eliador2001
0 Replies
2. Programming
Hi I want to implement the nice command in the shell that I am building. I came to know that there is a corresponding nice() system call for the same. But since I will be forking different processes to run different commands typed on the command prompt, is there any way I can make a command... (2 Replies)
Discussion started by: tejbuch
2 Replies
3. UNIX for Dummies Questions & Answers
hello everybody:
I have some job running on tru64 system and Im the root, due to limited resources I end up with my job ( vdump) for example taking the lowest share, I researched the nice command on the net, but couldnt get enough info, can I use it to already running process or I only use it... (1 Reply)
Discussion started by: aladdin
1 Replies
4. HP-UX
Hi,
I have two identical 12 CPU HPUX machines, and I run the same processes on each that load the boxes fully.
top on one reports activity under the NICE (19%) and SYS (18%) columns, while top on the other reports 0% NICE and 16% SYS. What would cause NICE to be zero on one machine and not... (5 Replies)
Discussion started by: CBorgia
5 Replies
5. Linux
Hi, new here and need some help. Sometimes my site is extremely slow, if when there aren't too many people on, whereas when there are over 300 online members the site may be very fast. We use CentOS, PHP 5.26. The server has 4GB and Plesk usually shows about 2 or 3 GB free.
I believe I can see... (4 Replies)
Discussion started by: pspace
4 Replies
6. AIX
Is there a 'top' command equivalent in AIX 4.2 ?
I already checked and I do not see the following ones anywhere:
top
nmon
topas (1 Reply)
Discussion started by: Browser_ice
1 Replies
7. UNIX for Advanced & Expert Users
Hello,
Some guy said to me that using the nice command to decrease the priority of a process is a myth, that the operating system corrects the priorities as the processes need cpu. Is this true? (4 Replies)
Discussion started by: psimoes79
4 Replies
8. Shell Programming and Scripting
Hello folks,
I am searching for pattern, after that i want its presenece on top to bottom basis, like
cat abcd.txt |grep "123"|awk {'print $3'} |sort|uniq -c
it show result like
10 1.1.1.1
1 1.1.1.1
15 1.1.1.1
100 1.1.1.1
but i want to see this like
100 1.1.1.1
15 1.1.1.44
10... (3 Replies)
Discussion started by: learnbash
3 Replies
9. HP-UX
Running 2 VM Guests on an HPUX Integrity Server. One Guest runs great, the other is always at a high NICE value and 0% idle as shown in TOP:
What do you think should be tuned to bring down the NICE and increase IDLE %? Thanks in advance
-hpuxadmin
slow VM GUEST
Load averages: 2.56,... (5 Replies)
Discussion started by: hpuxadmin
5 Replies
10. Shell Programming and Scripting
Dear Friends,
I have a directory when i take du of that directory it takes alot of memory and cpu and I/O, i want to use nice to run my script that have du command slowly so it won't take I/O and cpu, please suggest. (6 Replies)
Discussion started by: learnbash
6 Replies
AT(1) General Commands Manual AT(1)
NAME
at - execute commands at a later time
SYNOPSIS
at [ -c ] [ -s ] [ -m ] time [ day ] [ file ]
DESCRIPTION
At spools away a copy of the named file to be used as input to sh(1) or csh(1). If the -c flag (for (csh(1))) or the -s flag (for (sh(1)))
is specified, then that shell will be used to execute the job; if no shell is specified, the current environment shell is used. If no file
name is specified, at prompts for commands from standard input until a ^D is typed.
If the -m flag is specified, mail will be sent to the user after the job has been run. If errors occur during execution of the job, then a
copy of the error diagnostics will be sent to the user. If no errors occur, then a short message is sent informing the user that no errors
occurred.
The format of the spool file is as follows: A four line header that includes the owner of the job, the name of the job, the shell used to
run the job, and whether mail will be set after the job is executed. The header is followed by a cd command to the current directory and a
umask command to set the modes on any files created by the job. Then at copies all relevant environment variables to the spool file. When
the script is run, it uses the user and group ID of the creator of the spool file.
The time is 1 to 4 digits, with an optional following `A', `P', `N' or `M' for AM, PM, noon or midnight. One and two digit numbers are
taken to be hours, three and four digits to be hours and minutes. If no letters follow the digits, a 24 hour clock time is understood.
The optional day is either (1) a month name followed by a day number, or (2) a day of the week; if the word `week' follows, invocation is
moved seven days further off. Names of months and days may be recognizably truncated. Examples of legitimate commands are
at 8am jan 24
at -c -m 1530 fr week
at -s -m 1200n week
At programs are executed by periodic execution of the command /usr/libexec/atrun from cron(8). The granularity of at depends upon the how
often atrun is executed.
Error output is lost unless redirected or the -m flag is requested, in which case a copy of the errors is sent to the user via mail(1).
FILES
/usr/spool/at spooling area
/usr/spool/at/yy.ddd.hhhh.* job file
/usr/spool/at/past directory where jobs are executed from
/usr/spool/at/lasttimedone last time atrun was run
/usr/libexec/atrun executor (run by cron(8))
SEE ALSO
atq(1), atrm(1), calendar(1), sleep(1), cron(8)
DIAGNOSTICS
Complains about various syntax errors and times out of range.
BUGS
Due to the granularity of the execution of /usr/libexec/atrun, there may be bugs in scheduling things almost exactly 24 hours into the
future.
If the system crashes, mail is not sent to the user informing them that the job was not completed.
Sometimes old spool files are not removed from the directory /usr/spool/at/past. This is usually due to a system crash, and requires that
they be removed by hand.
4th Berkeley Distribution October 21, 1996 AT(1)