|
Problem IT44033
|
Status: Closed |
SMX_PING_INTERVAL SETTING PING MECHANISM CAN BE VERY CPU EXPENSIVE WHEN ELAPSED TIME REACHED CAUSING PERFORMANCE SPIKES
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
Since we start SMX threads from 14.10.xC6 and upwards for ER, on
a single CPU VP the ping timeout checking mechanism seems pretty
CPU expensive and creating spikes. See the # of scheds from
onstat -g cpu for the smxrcv thread.
$ onstat -g cpu -r 1|grep smxr
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:54 0.0004
3 sleeping secs: 21
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 21
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 20
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 19
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 18
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 17
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 16
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 15
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 14
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 13
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 12
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 11
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 10
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 9
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 8
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 7
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 6
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 5
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 4
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 3
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 2
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:48:55 0.0005
5 sleeping secs: 1
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 21
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 20
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 19
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 18
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 17
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 16
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 15
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 14
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 13
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 12
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 11
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 10
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 9
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 8
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 7
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 6
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 5
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 4
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 3
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 2
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:16 0.0918
540521 sleeping secs: 1
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:37 0.5919
4597057 running
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:38 1.0917
8915947 sleeping secs: 21
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:38 1.0917
8915947 sleeping secs: 20
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:38 1.0917
8915947 sleeping secs: 19
99 smxrcv_ol_1210_14_st 1cpu 06/21 08:49:38 1.0917
8915947 sleeping secs: 18 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC11. *
**************************************************************** |
| Local Fix: |
Setting SMX_PING_INTERVAL to 0 will prevent the SMX threads from
starting.
Setting CDR_FEATURES NOSMX4ER works same as above; no SMX
threads started for ER. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC11. *
**************************************************************** |
| Comment |
Fixed in Informix Server 14.10.xC11. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.06.2023
03.06.2024
03.06.2024 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
