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 LINUX
s390_runtime_instr
S390_RUNTIME_INSTR(2) System Calls Manual S390_RUNTIME_INSTR(2)NAME
s390_runtime_instr - enable/disable s390 CPU run-time instrumentation
SYNOPSIS
#include <asm/runtime_instr.h>
int s390_runtime_instr(int command, int signum);
DESCRIPTION
The s390_runtime_instr() system call starts or stops CPU run-time instrumentation for the calling thread.
The command argument controls whether run-time instrumentation is started (S390_RUNTIME_INSTR_START, 1) or stopped (S390_RUN-
TIME_INSTR_STOP, 2) for the calling thread.
The signum argument specifies the number of a real-time signal. The real-time signal is sent to the thread if the run-time instrumentation
buffer is full or if the run-time-instrumentation-halted interrupt occurred.
RETURN VALUE
On success, s390_runtime_instr() returns 0 and enables the thread for run-time instrumentation by assigning the thread a default run-time
instrumentation control block. The caller can then read and modify the control block and start the run-time instrumentation. On error, -1
is returned and errno is set to one of the error codes listed below.
ERRORS
EINVAL The value specified in command is not a valid command or the value specified in signum is not a real-time signal number.
ENOMEM Allocating memory for the run-time instrumentation control block failed.
EOPNOTSUPP
The run-time instrumentation facility is not available.
VERSIONS
This system call is available since Linux 3.7.
CONFORMING TO
This Linux-specific system call is available only on the s390 architecture. The run-time instrumentation facility is available beginning
with System z EC12.
NOTES
Glibc does not provide a wrapper for this system call, use syscall(2) to call it.
SEE ALSO syscall(2), signal(7)Linux Programmer's Manual 2012-12-17 S390_RUNTIME_INSTR(2)