Performance considerations for WebSphere Service Registry and Repository
John_Zoltek 120000CESP Visits (2284)
There are many things to consider in the area of WebSphere Service Registry and Repository (WSRR) performance. It is best to take a holistic approach and look at the entire set of components that make up environment where WSRR is installed. The first thing to consider is the hardware. WSRR does not provide specific hardware requirements. WSRR relies on the hardware requirements for WebSphere Application Server (WAS) because, after all, WSRR does run inside WAS. See WebSphere Application Server detailed system requirements for a list of the minimum and the recommended hardware requirements for a system that runs WAS. Consider the values listed as requirements for WSRR.
The second thing to consider is the version of WSRR you are running. Each version of the product has been improved in the area of performance. Version 8 is the latest version of the product and is the best version to run if performance is your goal. The biggest two areas of improvement in version 8 are in promotion and in the Business Space UI. You can read about version 8 here in the WSRR V8 Announcement Letter. If you are running 7.5 you should at the minimum be running on Fixpack 2. Fixpack 2 contains several APARs improving performance including IV03597, IV07613, and IV10021.
A third consideration is the software that WSRR depends upon. Tuning WebSphere Application Server and your database will help WSRR run faster. In the area of the database, running runstats and the reorg commands on a regular basis will improve performance by making the WSRR queries faster. This will improve performance in WSRR in the areas of document loading and promotion. Below you will find a link to a discussion about the runstats command. Tuning WAS is also important. Promoting or loading large amounts of complex objects takes time. There are several timeout values that you need to adjust to allow time for the promotion or load to complete. Below you will find two links discussing the various timeouts available. You will also find a link discussing the maximum heap size. This value may need to be increased if you are using WSRR heavily. If the heap is too small the system will slow down waiting for the garbage collector to clean up. Also be sure you are running supported versions of the database, database driver, and WAS. Please see the supported software link below. The tables to run runstats and reorgs are as follows:
Runstats Command Discussion: (external link) Runstats - What and Why
Supported Software: WebSphere Service Registry and Repository system requirements
Tuning WAS: Configuring WebSphere Application Server
Finally network latency can cause significant slowdowns in WSRR. WSRR makes many HTTP requests during normal operation. If TCP/IP response times are high the time it takes to complete the set of requests goes up resulting in poor performance. WSRR also makes many queries to the database. Again if response times are high performance suffers. Have your network engineer check the response times between the server where WSRR is running and the server where the database you are using is running and minimize the response time. Version 8 of WSRR has been drastically improved to reduce the number of requests which minimizes the effect a slow network has on WSRR. This improvement shows up best in the Business Space UI. If you are going to use Business Space we recommend you use WSRR version 8.
Reviewing all of these considerations in your environment will help you improve the performance of your WSRR install and provide a better overall product experience.