How To
Summary
This document describes the resources required on a Kubernetes cluster to support a small, medium, or large deployment of FileNet Content Manager or IBM Content Foundation in a containerized environment.
Objective
Use the attached Microsoft Excel workbook to calculate the cpu, memory, and pod requirements to support the expected workload of your FileNet Content Manager or IBM Content Foundation deployment.
In the spreadsheet, cpu sizing is provided in milliseconds (m) and memory sizing is provided in Memory in millibytes (Mi) with a byte size of 1024.
Environment
Many factors contribute to the resource estimations described in this workbook and IBM does not guarantee comparable values can be used in all situations. Performance numbers vary greatly depending upon system configuration and workload. The information contained in this publication was derived under specific operating and environmental conditions. While IBM has reviewed the information for accuracy under the given conditions, the results obtained in your operating environments might vary significantly. Accordingly, IBM does not provide any representations, assurances, guarantees, or warranties regarding performance.
Examples of when adjustments to the suggested sizing might be needed include
- When not all the containers are used in every workload. If a feature, such as external sharing of documents, or an API, such as Content Services GraphQL, is not used, that container requires less resources and might not need to be deployed.
- In high-volume content indexing scenarios (where a large percentage of the ingested documents is full text indexed) the Content Search Services utilization can substantially exceed the Content Platform Engine utilization.
- When optional processing occurs, such as thumbnail generation or text filtering, at least 1 GB of native memory is required by the Content Platform Engine for each type of processing. If both types of processing are expected, add at least 2 GB to the memory requests and limits for the Content Platform Engine.
- Using Navigator plug-ins, such as the External Data Service, requires increased memory and processor settings.
- Processing complex and large documents requires more memory and CPU for both Content Platform Engine and Content Search Services.
- Resource requirements might also increase over time as the amount of data in the system grows.
Steps
Pick a deployment profile (sc_deployment_profile_size) and enable the profile during installation. The FileNet Content Manager container environment provides small, medium, and large deployment profiles. You can set the profile when performing a new installation, installing an update, or performing an upgrade. The default profile is small.
Additional Information
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
13 June 2022
UID
ibm16526048