Cloud CM-IPMP Anleitung zur Fehlerbehebung Seite 66
- Seite / 201
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Parameter Set Type Tunable Parameters
Object Pools Object Pool Sizing
Staging Threads Staging Configuration
Memory Database Sizing Memory Database Size limits
System Memory Usage JVM Heap Size
Lock Manager Lock Strategy
Table 8.1: Useful statistics for tuning Rhino performance
• Gauges show the quantity of a particular object or item such as the amount of free memory, or the number of active
activities.
• Sample type statistics collect sample values every time a particular event or action occurs. Examples of sample type
statistics are event processing time, or lock manager wait time.
Counter and gauge type statistics are read as absolute values while sample type statistics are collected into a frequency distri-
bution and then read.
8.2 Performance Implications
The statistics subsystem is designed to minimise the performance impact of gathering statistics. Generally, gathering counter
or gauge type statistics is very cheap and should not result in more than 1% impact on either overall CPU usage or latency even
when several parameter sets are monitored. Gathering sample type statistics is more costly and will usually result in a 1-2%
impact on CPU usage when several parameter sets are monitored.
It is not recommended that the client be executed on production cluster node. Rather, run the statistics client on a local
workstation. The statistics client’s GUI can result in CPU usage that may cause a cluster to drop calls.
The exact performance impact depends on the number of distinct parameter sets being monitored, the number of simultaneous
users, and the sample frequency.
8.2.1 Direct Connections
For collecting statistics from a Rhino cluster, the
rhino-stats
client asks each node to create a connection back to the statistics
client for the express purpose of sending the client statistics data. This requires each Rhino node to be able to create outgoing
connections to the host that the
rhino-stats
client is running on, so an intermediary firewalls will need to be configured to
allow this.
Previous versions of the statistics client retrieved statistics by creating a single outgoing JMX connection to one of the cluster
nodes. This statistics retrieval method is now disabled by default, as it had a greater performance impact than when using direct
connections. It is still available through the use of the
-j
option.
8.3 Console Mode
In console mode the
rhino-stats
client has two main modes of execution. When run with the
-l
parameter
rhino-stats
will list the available types of statistics the Rhino SLEE is capable of supplying.
The following examples show usage of
rhino-stats
to query available parameter set types, and to query the available param-
eter sets within the parameter set type
Events
[user@host rhino]$ ./client/bin/rhino-stats -l
The following parameter set types are available for instrumentation:
Activities, Events, Lock Managers, MemDB-Local, MemDB-Replicated, Object Pools,
Services, Staging Threads, System Info, Transactions
For parameter set type descriptions and a list of available parameter sets use
-l <type name>
option
Open Cloud Rhino 1.4.3 Administration Manual v1.1 57
- Open Cloud Rhino SLEE 1.4.3 1
- Administration Manual 1
- November 2, 2006 (1838) 2
- Contents 3
- Introduction 10
- The Rhino SLEE Platform 12
- 2.3 Integration 13
- 2.4 Service Development 14
- 2.5 Functional Testing 15
- 2.6 Performance Testing 15
- 2.7 Software Development Kit 16
- JAIN SLEE Overview 17
- 3.3 Event Driven Applications 18
- 3.4 Components 18
- 3.5 Provisioned Data 18
- 3.6 Facilities 18
- 3.7 Activities 19
- 4.2.3 Firewalls 22
- 4.2.4 Unpacking 22
- 4.2.5 Installation 22
- 4.2.6 Unattended Installation 23
- 4.2.7 Configuring a Cluster 23
- 4.2.9 Configuring the Cluster 25
- 4.3 Cluster Lifecycle 26
- 4.3.2 Starting a Node 27
- 4.3.3 Starting a Quorum Node 27
- 4.3.4 Automatic Node Restart 27
- 4.3.5 Starting the SLEE 27
- 4.4 Management Interface 28
- 4.5 Setting the system clock 29
- 4.6 Optional Configuration 30
- 4.7 Installed Files 31
- 4.8 Runtime Files 32
- 4.8.2 Logging output 33
- Management 35
- 5.2 Management Tutorials 36
- 5.3 Building the Examples 37
- 5.5 Installing a Service 40
- 5.6 Uninstalling a Service 43
- 5.8 Creating a Profile 46
- 5.9 SLEE Lifecycle 50
- 5.9.4 The Stopping State 51
- 5.9.2 The Starting State 51
- 5.9.3 The Running State 51
- Administrative Maintenance 52
- 6.2.2 Removing Activities 54
- 6.2.3 Inspecting SBBs 55
- 6.2.4 Removing SBB Entities 56
- 6.2.5 Removing All 56
- 6.3 Upgrading a Cluster 57
- 6.3.3 Deploying State 58
- 6.4 Backup and Restore 59
- Export and Import 60
- 7.2 Exporting State 61
- 7.3 Importing State 62
- 7.4 Partial Imports 63
- Statistics and Monitoring 65
- 8.2 Performance Implications 66
- 8.3 Console Mode 66
- 8.3.1 Useful output options 67
- 8.4 Graphical Mode 68
- Web Console 73
- 9.2.2 Managed Objects 74
- 9.2.3 Navigation Shortcuts 74
- 9.3 Deployment Architecture 75
- 9.3.2 Standalone Web Console 76
- 9.4 Configuration 77
- 9.5 Security 77
- 9.5.2 Declarative Security 78
- 9.5.3 JAAS 78
- Log System Configuration 79
- 10.3 Logging Configuration 80
- 10.3.2 Web Console Logging 81
- Chapter 11 84
- 11.2.2 Web Console 85
- Threshold Alarms 87
- 12.5 Types of Rule Conditions 88
- 12.6 Creating Rules 89
- 12.6.2 Command Console 90
- Chapter 13 92
- 13.3.1 Configuration 93
- Licensing 94
- 14.2 Alarms 95
- 14.2.4 Management Interface 96
- 14.2.5 Audit Logs 96
- Security Configuration 97
- 15.3 Network Connections 98
- 15.4 Signing Deployable Units 99
- 15.5 Key Stores 100
- 15.6 Transport Layer Security 100
- 15.7 JAAS Configuration 101
- Performance Tuning 103
- 16.2.3 Tuning Recommendations 104
- 16.2.1 Configuration 104
- 16.2.2 Stage Tuning 104
- 16.3 Object Pool Configuration 105
- 16.4 Fault Tolerance 106
- Clustering 109
- 17.3 Scenarios 110
- 17.4 Configuration Parameters 111
- Application Environment 113
- 18.2.2 Concurrency Control 114
- 18.3 Application Configuration 115
- 18.5.4 Example 119
- 18.6 Application Fail-Over 120
- 18.6.2 Management Interface 121
- Database Connectivity 122
- 19.3 Configuration Example 123
- 19.4 SBB use of JDBC 124
- 19.4.1 SQL Programming 125
- J2EE SLEE Integration 127
- PostgreSQL Configuration 131
- 21.4 TCP/IP Connections 132
- 21.5 Access Control 132
- SIP Example Applications 138
- 22.2 System Requirements 139
- 22.3 Directory Contents 139
- 22.4 Quick Start 139
- 22.4.2 Building and Deploying 140
- 22.5 Manual Installation 144
- 22.6 Using the Services 152
- 22.6.4 Enabling Debug Output 156
- JCC Example Application 157
- 23.2.1 Resource Adaptor 158
- 23.2.3 Service Logic 160
- 23.3 Directory Contents 163
- 23.4 Installation 163
- 23.6.1 Trace Components 170
- 23.6.3 Creating a Call 171
- 23.7 Call Duration Service 172
- Customising the SIP Registrar 178
- 24.4 Extending with Profiles 181
- Hardware and Systems Support 182
- A.2.4 Application Example 184
- Redundant Networking 186
- Entities 191
- C.3 Configuration Properties 192
- C.4 Entity Binding 193
- Transactions 194
- D.3.3 Summary 195
- D.4.3 Commit Protocols 196
- Audit Logs 197
- E.2 Example Audit Logfile 199
- Glossary 200
© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.067 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern