Professional Documents
Culture Documents
1 PDF counters
This section provides system characterisation data with respect to enabling the
Probability Density Function (PDF) counters as part of the Ericsson UTRAN P7.1
Tech Pack. The figures presented below show the difference in activating 7.1 PDF
counters on the 7.1 Tech Pack for a specific environment that is in turn detailed in the
next section. Due to the large number of counters that are PDF counters and which are
being introduced as part of this release, the information provided below should be
used when deciding what the projected system impact would be by enabling PDF
counters on the Ericsson UTRAN Tech Pack. By default, all PDF counters are
deactivated in the gateway configuration. Please consult the Tech Pack gateway
documentation for guidance of how to activate and deactivate the PDF counters.
Setup
Sample Data used during Characterisation
The Ericsson UTRAN P7.1 characterisation results presented below are based on a
UTRAN that consists of 20 RNCs and 4000 NodeBs, all feeding performance
management (PM) data related to 12000 cell instances to a single 9.2 TNPMW
instance. System characterisation measurements were also performed on PM data
being feed to a baseline Tech Pack in parallel to feeding PM data the Ericsson
UTRAN 7.1 Tech Pack. These measurements were used to show the impact of
processing PDF counters has on other Tech Packs that are also installed on the same
TNPMW instance. The Siemens UTRAN UMR 6.5 was used as the baseline Tech
Pack.
Hardware Environment
The hardware configuration that was used to characterise the impact of PDFs is
depicted in Table 1:
120
CPU Precentage Utilisation
100
User
80
System
60 Idle
Wait
40
Stolen
20
0
16:00:00
16:15:40
16:31:20
16:47:00
17:02:40
17:18:20
17:34:00
17:49:40
18:05:20
18:21:00
18:36:40
18:52:20
19:08:00
19:23:40
19:39:20
19:55:00
20:10:50
20:26:30
20:42:10
20:57:50
21:13:30
21:29:10
21:44:50
22:00:30
22:16:10
22:31:50
22:47:30
23:03:10
23:18:50
23:34:30
23:50:10
800
700
600
oradata01
IOSTAT w_ps
500 oradata02
400 oradata03
300 oradata04
Total_w _ps
200
100
0
16:00:00
16:16:30
16:32:50
16:49:10
17:05:30
17:21:50
17:38:10
17:54:30
18:10:50
18:27:10
18:43:30
18:59:50
19:16:10
19:32:30
19:48:50
20:05:10
20:21:30
20:37:50
20:54:10
21:10:30
21:26:50
21:43:10
21:59:30
22:15:50
22:32:10
22:48:30
23:04:50
23:21:10
23:37:30
23:53:50
Tim e (10 second sam pling)
120
CPU Precentage Utilisation
100
User
80
System
60 Idle
Wait
40
Stolen
20
0
16:00:00
16:15:40
16:31:20
16:47:00
17:02:40
17:18:20
17:34:00
17:49:40
18:05:20
18:21:00
18:36:40
18:52:20
19:08:00
19:23:40
19:39:20
19:55:00
20:10:50
20:26:30
20:42:10
20:57:50
21:13:30
21:29:10
21:44:50
22:00:30
22:16:10
22:31:50
22:47:30
23:03:10
23:18:50
23:34:30
23:50:10
The CPU utilisation for the loader server measured approximately 5% when the PDF
counters were disabled as opposed to approximately 11% when the PDF counters
were enabled. Even though there is approximately 100% increase on the loader server
CPU utilisation, the loader sever overall resource utilisation is still very low. Figure 4
and Figure 5 illustrates the impact of enabling PDF counters on the loader server IO
statistics. Similarly to the other graphs already presented, the first half of both these
graphs exhibit the IO behaviour when the PDF counters are enabled and the second
half shows the behaviour when the PDF counters are disabled.
IOSTAT w_ps IOSTAT r_ps
0
100
200
300
400
500
600
0
200
400
600
800
1000
1200
1400
16:00:00
16:00:00
16:16:10
16:16:20
16:32:10
16:32:30
16:48:10
16:48:40
17:04:10
17:04:50
17:20:10
17:21:00
17:36:10
17:37:10
17:52:10
17:53:20
18:08:10
18:09:30
18:24:10
18:25:40
18:40:10
18:41:50
18:56:10
18:58:00
19:12:10
19:14:10
19:28:10
19:30:20
19:44:10
19:46:30
20:00:10
20:02:40
20:16:10
20:18:50
20:32:10
20:35:00
20:48:10
IOSTAT r_ps T010909
20:51:10
Tim e (10 second sampling)
21:04:10
21:07:20
Figure 4 Loader Server IO Read statistics
21:20:10
21:23:30
21:36:10
21:39:40
21:52:10
21:55:50