Cloud CM-IPMP Guía para resolver problemas Pagina 104
- Pagina / 201
- Tabla de contenidos
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
16.2.1 Configuration
Configure the following parameters for staging configuration using the Web Console, or by editing and updating the staging
configuration XML using the Command Console.
1.
local-enabled
2.
local-maximum-size
3.
maximum-age
4.
maximum-size
5.
threadcount
16.2.2 Stage Tuning
You can observe the effects of the configuration changes in the Statistics Client by simulating heavy concurrency using a load
simulator.
For more information regarding statistics please refer to Chapter 8
16.2.3 Tuning Recommendations
The maximum size of the staging queue determines how many stage items may be queued awaiting processing. When the
queues maximum size is reached the oldest item in the queue is automatically failed and removed to accommodate new items.
The default value of 3000 is suitable for most scenarios. It is recommended to set the maximum size to be high enough that the
SLEE can ride out short bursts of peak traffic, but not so large that under extreme overload stage items are allowed to wait in
the queue for too long before being properly failed.
The
thread-count
parameter determines the number of staging threads that will service the staging queue. This parameter
has the greatest impact on overall latency of all the staging parameters and careful attention should be given to tuning the
thread-count
in order to achieve optimal performance. Again, is has been found the default value of 30 to be useful for many
applications on a wide range of hardware, however for some applications, or when using hardware with 4 or more CPU’s it may
be beneficial to increase the number of staging threads.
In particular when the SLEE is running services that perform high latency blocking requests to an external system it will often
be necessary to increase the number of staging threads.
Consider for example a credit check application that will only allow a call setup to continue after performing a synchronous call
to an external system. If a credit check takes on average 150ms this means the staging thread processing the call setup event will
be blocked and unable to process other events for 150ms. With the default configuration of 30 staging threads such a system
would be able to handle an input rate of approximately 200 events/second. Above this rate the stage worker threads will not
be able to service event processing stage items fast enough and stage items will begin to backup in staging queues, eventually
causing some calls to be dropped. In this example the problem is easily solved by configuring additional staging threads.
In real world applications it is seldom a matter of applying a simple formula to work out the optimal number of staging threads,
it is recommended to use performance monitoring tools to examine the behaviour of staging alongside such metrics as event
processing time and system CPU usage to find a suitable value for this parameter.
The
maximum-age
setting determines the maximum time an item of work can remain in the staging queue and still be consid-
ered valid for processing upon removal. Tuning of this parameter (along with
maximum-size
) is useful for determining your
application’s behaviour under overload conditions.
The
local-enabled
,
local-initial-size
and
local-maximum-size
parameters are useful for reducing latency and, to a
lesser extent, CPU usage in some applications by controlling thread affinity for related items of work. These parameters become
useful when an event processing stage item is submitted to staging by a staging thread. This would happen for example if SBB
event handler code being executed on a particular staging thread fires an event using an SBB fireXXEvent() method and the
transaction commits.
With local staging queues disabled the stage item for the fired event will enter the staging queue just like any other event.
Open Cloud Rhino 1.4.3 Administration Manual v1.1 95
- 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.es. Todos los derechos reservados | 0.056 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales