Chapter 8. Management and Performance Tuning
CloudTran is a high-performance, multi-threaded system. It benefits from tuning for each deployment and range of loads.
Doing this one run at a time is difficult and time-consuming.
To make tuning quicker and easier,
CloudTran supports JMX
management beans (MBeans). This shows key performance parameters (e.g. the average time taken for a logger write),
and lets you change the control parameters (e.g. the disk write delay time).
Performance parameters tend to be numeric, and these attributes can be seen on a graph:
Another example: the number of persist threads per datasource may
be too low for your application. You can increase the number of persist threads
one at a time. At some point, say 5 threads, there is no performance increase,
so it is safe to use 4 in the permanent configuration.
This can be done in seconds rather than hours,
so you can very quickly find the optimum configuration settings for a deployment.
Note that changes you make through MBeans are not permanent.
You will have to record the settings manually and then change the permanent
configuration properties for a deployment.
However, it is worth noting that skilled operators may choose to tune
CloudTran at run time as conditions change; this obviously needs careful preparation and control.
To work with CloudTran MBeans, you can use the JDK utility
The attributes are separated into beans called MBeans, some bean contains attributtes about several parts of the application, some of them
are specific and only describe a certain, well defined part of the application.
8.1 How to launch and use JConsole
8.2 Management bean overview
8.3 The most significant attributes
8.4 The Application life cycle bean
8.5 The Coordinator bean
8.6 The Datasource bean
8.7 The Resolve transactions to cohorts bean
8.8 The Cohort bean
8.9 The Coordinator crash test bean
8.10 The Cohort crash test bean