免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
123
最近访问板块 发新帖
楼主: studio99

[性能调优] to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80 [复制链接]

论坛徽章:
0
发表于 2003-09-19 14:48 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

online.log
18:27:05  Logical Log 16951 Complete.
18:27:07  Process exited with return code 154: /bin/sh /bin/sh -c /home/informix/etc/log_full.sh 2 23 "Logical Log 16951 Complete." "Logical Log 16951 Complete."
18:30:57  Checkpoint Completed:  duration was 4 seconds.
18:30:57  Checkpoint loguniq 16952, logpos 0x76c018

18:36:16  Checkpoint Completed:  duration was 1 seconds.
18:36:16  Checkpoint loguniq 16952, logpos 0x1147018

18:40:51  Assert Failed: Unexpected virtual processor termination, pid = 110134, exit = 0x18

18:40:51  Informix Dynamic Server Version 7.31.UD1   
18:40:51   Who: Session(58104, bankrun@czxh1, 106842, 0)
                Thread(52, kaio, 0, 1)
                File: mt.c Line: 10879
18:40:51  Internal error detected in notify_vp
18:40:51  PANIC: Attempting to bring system down

Sun Apr  6 18:41:13 2003

18:41:13  Event alarms enabled.  ALARMPROG = '/home/informix/etc/log_full.sh'
18:41:18  DR: DRAUTO is 0 (Off)
18:41:18  AIX MP latch code enabled
18:41:18  Dynamically allocated new message shared memory segment (size 1104KB)

18:41:18  Dynamically allocated new message shared memory segment (size 1104KB)

18:41:18  Dynamically allocated new message shared memory segment (size 1104KB)

18:41:18  Dynamically allocated new message shared memory segment (size 1104KB)

18:41:18  Informix Dynamic Server Version 7.31.UD1    Software Se
18:41:18  
18:41:19  (17) connection rejected - no calls allowed for sqlexec
18:41:19  ( connection rejected - no calls allowed for sqlexec
18:41:19  (14) connection rejected - no calls allowed for sqlexec
18:41:19  (11) connection rejected - no calls allowed for sqlexec
18:41:19  listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode.

18:41:19  listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode.

18:41:19  listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode.

18:41:19  (20) connection rejected - no calls allowed for sqlexec
18:41:19  (22) connection rejected - no calls allowed for sqlexec
18:41:19  listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode.

论坛徽章:
5
荣誉会员
日期:2011-11-23 16:44:17CU大牛徽章
日期:2013-09-18 15:15:15CU大牛徽章
日期:2013-09-18 15:15:45未羊
日期:2014-02-25 14:37:19射手座
日期:2014-12-26 22:55:37
发表于 2003-09-19 21:50 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

原帖由 "studio99" 发表:
online.log
18:27:05  Logical Log 16951 Complete.
18:27:07  Process exited with return code 154: /bin/sh /bin/sh -c /home/informix/etc/log_full.sh 2 23 "Logical Log 16951 Complete." "Logical Log 1695..........
   
你的onconfig肯定有问题,老是动态增加共享内存段。
贴出来。
另外你们的系统宕机的时候在/tmp/下面的af文件呢,应该发给IBM看看。
你么是不是没有买INFORMIX的服务啊,还是根本就是盗版?

论坛徽章:
0
发表于 2003-09-19 22:36 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

不知道这个对于 CPU Time Limit有没有用?
Cpu time limit

                                     Revised: February 2001
Cpu time limit
Each account is set up with a default limit for the maximum amount
of processor time a task may use.  If a task runs over the limit
it is terminated with the message
       Cputime limit exceeded
The purpose of the limit is to prevent background tasks which are
left running after logout from inadvertently running "forever".
Some tasks may legitimately require more cpu time than the default
limit.
AD HOC CPU LIMIT ADJUSTMENTS
A temporary limit change may be made by typing at the shell (%)
cpulimit 3600
Note that the "cpulimit" command is an alias defined either in your
.cshrc file or in /public/cshrc.adjunct which is sourced by your
.cshrc file.  If you get "cpulimit: Command not found", you can add
this alias to your .cshrc file and then re-login,
alias cpulimit  'setenv CPU \!*; limit cpu $CPU'
"cpulimit 3600" limits subsequent tasks, in the current session,
making sure they do not individually exceed 3600 seconds of processor
time.
The cpu limit can be turned off altogether (not a very good idea unless
you are certain that you do not have a runaway job) by typing at the
shell (%)
unlimit cpu
CHANGING THE DEFAULT CPU LIMIT
You can change the default cpu limit for your account by adding
a line like "cpulimit 3600" to the *end* of your .login and .cshrc
files.  [Actually only one or the other is necessary, but putting
the command both places will save you the trouble of figuring out
which one is appropriate for your system.]
Instructors or TAs can modify the cpu limit for all the students in a
class.  The technique depends on the system type and whether or not
the course is set up using the OCE model.  You may want to seek
assistance from ACS ( acs-consult.ucsd.edu ), but briefly, if the
the course is using the OCE model, put the cpulimit command
(e.g. "cpulimit 3600" in the prepfile for the course.  Otherwise
the cpulimit command needs to be placed in the locallogin or localcshrc
file for the course, depending on the system type.  Putting it in both
will do the job and should not cause any problems.
AVOIDING PROBLEMS WITH CPU LIMIT WHEN EDITING
It is painful to have an editing session terminate due to the cputime
limit, particularly if you are in visual mode.  The terminal is left in
a strange state where characters are not echoed, and the LINEFEED key
must be used instead of RETURN.  If you ever "bomb" out of visual, try
typing LINEFEED reset LINEFEED.
To avoid the possibility of running out of cpu time while editing, most
accounts have an alias specified for vi which temporarily unlimits cpu
time during visual editing sessions.  See /public/cshrc for an example
of such an alias.
For more information regarding the command "limit" see "man csh".

论坛徽章:
0
发表于 2003-09-22 08:52 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

老兄不敢用盗版的呢,是正版.
thank you

论坛徽章:
0
发表于 2003-09-22 09:09 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

[quote]原帖由 "studio99"]会不会是informix 7.31 的BUG[/quote 发表:
   



升级你的informax吧。

论坛徽章:
0
发表于 2003-09-22 09:13 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

原帖由 "studio99" 发表:
老兄不敢用盗版的呢,是正版.
thank you
   


我建议你改用db2,是IBM的另一条贼船。

论坛徽章:
0
发表于 2003-09-22 11:56 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

onconfig   
# System Configuration

SERVERNUM       0               # Unique id corresponding to a Dynamic Server instance
DBSERVERNAME    online_bank     # Name of default database server
DBSERVERALIASES                 # List of alternate dbservernames
DEADLOCK_TIMEOUT 60              # Max time to wait of lock in distributed env.
RESIDENT        0               # Forced residency flag (Yes = 1, No = 0)

MULTIPROCESSOR  1               # 0 for single-processor, 1 for multi-processor
NUMCPUVPS       5               # Number of user (cpu) vps
SINGLE_CPU_VP   0               # If non-zero, limit number of cpu vps to one

NOAGE           0               # Process aging
### 030706 digital china
AFF_SPROC       0               # Affinity start processor
### 030706 digital china
AFF_NPROCS      0               # Affinity number of processors

# Shared Memory Parameters
LOCKS           1000000         # Maximum number of locks
BUFFERS         300000          # Maximum number of shared buffers
NUMAIOVPS       5               # Number of IO vps
PHYSBUFF        64              # Physical log buffer size (Kbytes)
LOGBUFF         196             # Logical log buffer size (Kbytes)
LOGSMAX         120             # Maximum number of logical log files
CLEANERS        8               # Number of buffer cleaner processes
SHMBASE         0x30000000L     # Shared memory base address
### 030706 digital china
SHMVIRTSIZE     250000          # initial virtual shared memory segment size
### 030706 digital china
SHMADD          8192          # Size of new shared memory segments (Kbytes)
SHMTOTAL        0               # Total shared memory (Kbytes). 0=>;unlimited
CKPTINTVL       300             # Check point interval (in sec)
LRUS            8               # Number of LRU queues
LRU_MAX_DIRTY   70              # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY   60              # LRU percent dirty end cleaning limit
LTXHWM          50              # Long transaction high water mark percentage
LTXEHWM         60              # Long transaction high water mark (exclusive)
TXTIMEOUT       0x12c             # Transaction timeout (in sec)
STACKSIZE       32              # Stack size (Kbytes)

论坛徽章:
0
发表于 2003-09-22 19:55 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

运行机_run>;ps aux|head
USER        PID %CPU %MEM   SZ  RSS    TTY STAT    STIME  TIME COMMAND
root        516 13.5  0.0   12 12416      - A      Aug 25 26305:04 kproc
root        774 12.4  0.0   12 12416      - A      Aug 25 24272:26 kproc
root       1032 12.2  0.0   12 12416      - A      Aug 25 23793:24 kproc
root       1806 12.1  0.0   12 12416      - A      Aug 25 23681:23 kproc
root       1290 12.1  0.0   12 12416      - A      Aug 25 23651:04 kproc
root       1548 12.1  0.0   12 12416      - A      Aug 25 23554:52 kproc
bankrun  102438  2.6  0.0 7280 4804      - A    12:44:37 17:43 oninit
bankrun  101504  2.5  0.0 6940 4792      - A    12:44:44 17:27 oninit
bankrun   93462  2.2  0.0 6928 4796      - A    12:44:44 15:29 oninit
运行机_run>;

论坛徽章:
5
荣誉会员
日期:2011-11-23 16:44:17CU大牛徽章
日期:2013-09-18 15:15:15CU大牛徽章
日期:2013-09-18 15:15:45未羊
日期:2014-02-25 14:37:19射手座
日期:2014-12-26 22:55:37
发表于 2003-09-22 21:11 |显示全部楼层

to 老农:各位老大帮忙分析一下系统性能 RS 6000 IBM M80

不对啊,你的onconfig和onstat -g seg输出不符合啊?
你先增加一下SHMVIRTSIZE,8G物理内存,你初始的才256M,弄个1G吧。
PAGE BUFFER也可以弄大点,不过你的IDS好像是32位的版本,在8G内存的机器上浪费了。
另外如果你你的系统是OLTP,适当的减小LRU_MAX_DIRTY
LRU_MIN_DIRYTY,到5和3吧。
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP