Component configuration recommendations for vertical scaling

Based on the recommended hardware sizes, you might need to change the configurations of various product components to make optimum use of available resources.

The following table provides a list of the configuration properties, their locations, and the recommended values for the properties for each setup.

Use the following table in conjunction with the recommendations provided in the vertical scaling recommendations.

Note that the values given in the following table are on a per component basis. For example, if you have three Indexers in your environment, then the value of 16000 MB for wrapper.java.initmemory will be applicable for each Indexer.

In the table, the configuration location paths must be preceded by one of the following environment variables:

  • Windows: %BMC_ITDA_HOME%
  • Linux: $BMC_ITDA_HOME

Related topics

Where to find more information

Variables that affect sizing and scalability

Sizing-and-scalability-considerations

Sizing-drivers-and-their-impact

FAQs-about-performance-and-scalability

Note

When you change any of the following properties, ensure that you re-start the corresponding service for the particular component and any dependent services. For example, the wrapper.java.initmemory property defines the initial memory required for the Indexer, so when you change this property value, ensure that you re-start the Indexer.

For more information about starting or stopping services and service dependencies, see Starting-or-stopping-product-services.

Ensure that you make the same configuration changes for components of the same type. For example, if you change certain configurations for the Indexer, and you have multiple instances of Indexers deployed, ensure that you make the change for all Indexers in your environment.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*