|When tuning your Mashup Center environment for optimum performance, you should tune and configure the individual systems and components used in your environment. This guide discusses some general concepts about performance tuning and describes the configuration details used in the measurement environments used by the IBM® performance team.
Contents: IBM Mashup Center Performance Tuning Guide
Download this content as a PDF file
Although Mashup Center is a single product, it is composed of the following two main components: Lotus® Mashups and MashupHub. The Lotus Mashups component includes the mashup builder environment where you create the pages and spaces that make up your mashup applications. The MashupHub component includes the catalog, data mashup builder, and set of feed generators. When tuning your environment, each of these components can be configured separately.
When tuning Lotus Mashups, we observed the following details during the benchmark testing:
- The main factor that affected performance was the speed of the WebSphere Application Server central processing unit (CPU). As a general rule, the faster the CPU, the higher the throughput.
- The Java virtual machine (JVM) heap did not restrict performance in the IBM testing environment.
- The bandwidth of our network did not restrict performance when using a 100–megabit network with browser cache settings and GZIP encoding. For more heavy workloads, we recommend that you connect a reverse proxy server such as IBM WebSphere Edge Server, IBM HTTP Server, and WebSphere Application Server using a 1000–megabit network.
- The throughput results from the IBM testing cannot be achieved with default settings.
We also observed some recommendations for tuning performance of MashupHub. For example, the level of performance mainly depends on the feeds in the catalog. This dependency is described in more detail at Tuning MashupHub feeds
. In addition, we observed the following details:
- When server-side cache is enabled for MashupHub feeds, performance is limited mostly by the database disk I/O or the MashupHub application server's CPU. As a general rule, increasing the number or speed of the database hard disks or application server CPU may result in increased throughput.
- In our testing environment, we found that the JVM heap did not restrict performance when the MashupHub feed cache was disabled. If your MashupHub feed cache is enabled, do not set server-side cache memory too large, and make sure that MashupHub has enough JVM heap. We recommend that you start at 25% of the maximum heap size
- Feed performance mainly depends on the computation complexity of the feed. As a general rule, the more complex the computation, the more limited the performance of the feed. Increasing the number or speed of the CPUs may increase feed throughput.
- MashupHub performance depends mainly on the size of the feeds. Larger feed sizes may decrease throughput.