There might be some problem with my server,
because every morning at 7, it's performance become bad with no DB extra deadlock.
But I just couldn't figure it out.
Please give me some advise, thanks a lot...
According to the CPU performace chart, Daily CPU loading Maximum: 42 %, Average:36%.
But I have a serious Report Delay for almost half hour.
Here is the "TOP", at the same time but the next day I collect.
How can I measure CPU loading (like performance monitor in Windows OS). I use Solaris but I would like to write portable code.
Besides, I have to write programm to load CPU with known percent. How can I use CPU in 30% for example.
Thanks for any ideas. (6 Replies)
Hi All,
Can you please help me in resolving the following problem?
My requirement is like this:
1) I have two files YESTERDAY_FILE and TODAY_FILE. Each one is having nearly two million data.
2) I need to check each record of TODAY_FILE in YESTERDAY_FILE. If exists we can skip that by... (5 Replies)
Hello guys!
I'm n00b in AIX and I'm sticked in a problem. (my English is poor enough, but I hope you can understand me :P). So.. I'm trying to connect to an AIX machine with putty, and .. 'using username xxx' appears after 2 sec (OK), but 'xxx@ip's password' appears after 1:15 min. After... (6 Replies)
Hi to all,
i have an app on solaris 5.8 writed in C++ (3.2.1) that use multi threading.
Hardware has 8 cpu. When i run my app i note that the average of cpu go at least at 40%, and the performance are not so higher..
There is a cpu limitation on solaris, that dedicate only a part of cpu... (3 Replies)
Hello All.
I have Sun T1000 server with Solaris 10.
On T1000 installed EMC smarts, application for monitoring network devices via SNMP + SNMP.
So, Smarts has own DB (contains object - devices and relationships), file takes 30 mb, now, all queries to DB works very slow, so Smarts works too slow,... (5 Replies)
Hi folks.
By disk cloning on Solaris x86, I used a command dd.
I pulled out the source and inserted the new disk.
By loading I have received the following issue: BAD PBR SIGN. :( (5 Replies)
I have written a virtual HBA driver named "xmp_vhba". A scsi disk is attached on it. as shown below:
xmp_vhba, instance #0
disk, instance #11
But the performance became very bad when we read/write the scsi disk using the vdbench(a read/write io tool).
What is the reason? ... (7 Replies)
Hello All
I have a system running AIX 61 shared uncapped partition (with 11 physical processors, 24 Virtual 72GB of Memory) .
The output from NMON, vmstat show a high run queue (60+) for continous periods of time intervals, but NO paging, relatively low I/o (6000) , CPU % is 40, Low network.... (9 Replies)
Hi,
We have a Solaris server that has about 43 Oracle databases on it and we also have the Oracle Enterprise Manager - emagent that is used to monitor these databases
When running top, the emagent is showing as one of the top process. Excerpts from running top shows something as below:
... (3 Replies)
Hi Guys,
I have fresh new installed VIO 2.2.3.70 on a p710, 3 physical SAS disks, rootvg on hdisk0
and 3 VIO clients through vscsi, AIX7.1tl4 AIX6.1tl9 RHEL6.5ppc, each lpar has its rootvg installed on a LV on datavg (hdisk2) mapped to vhost0,1,2
There is no vg on hdisk1, I use it for my... (1 Reply)
Discussion started by: frenchy59
1 Replies
LEARN ABOUT OPENDARWIN
queuedefs
queuedefs(4) File Formats queuedefs(4)NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO at(1), crontab(1), nice(1), cron(1M)SunOS 5.10 1 Mar 1994 queuedefs(4)