Performance overview
The performance of Global Mailbox is measured by the throughput speed of the transactions that flow through the system. You can tune the performance during and after the installation of Global Mailbox.
During installation
During the installation, you can tune the following items to improve the performance
of the application:
- Storage settings, including lifespan and buffer size. For more information, see Provisioning storage.
- Replication options - You can configure the system global replication
settings using a command line tool. You must understand the tradeoff
between performance and risk of data loss with the various settings as well
as the system impact of other settings like minimum segment size.
- Asynchronous or delayed replication -- best performance at the cost of increased risk of data loss
- Synchronous or immediate replication -- lowest risk of data loss at the cost of performance
- To at least one other data center - this is the official definition of synchronous replication for the Global Mailbox system
- To a quorum of data centers - to all data centers
- For more information, see Configuring payload replication and Administering Apache Cassandra.
After installation
After the installation, you can tune the following items to improve the performance
of the application:
- Purge functions. For more information, see Administering purge.
- Other scheduled jobs. For more information, see Administering scheduled jobs.
-
If it is possible to maintain strong consistency without altering your cluster topology, then there is no need to perform Cassandra maintenance. If maintenance is required, see Maintaining performance with Apache Cassandra.
- It is essential that the ZooKeeper ensemble topology is configured identically on each ZooKeeper node. Never start a ZooKeeper node unless this precondition is met. For more information, see Planning ZooKeeper maintenance.