Skip to main content

​
Overview

Details of specific measurements used to assess and quantify the resource utilization of LILT applications. These metrics provide insights into the performance, capacity, and scalability requirements of the applications. They include parameters such as CPU utilization, memory consumption, disk size and concurrent user sessions. By establishing baseline measurements and setting thresholds, usage-sizing metrics help identify normal operating levels and define boundaries for resource usage. These metrics enable proactive capacity planning, resource optimization, and the ability to detect anomalies or performance bottlenecks. The table below is meant to be a reference guide, and not an exact match to your individual environment, as each installation may choose to enable or disable specific services.

​
Usage-Sizing Metrics

*The following specifications are recommended for installing LILT on bare-metal hardware to support the given applications. It is important to note that these specifications may need to be adjusted based on the specific load requirements.
**To efficiently handle parallel batch requests, it is recommended to have the same number of GPUs as the number of required concurrent batch requests. This enables the system to effectively distribute the workload and process multiple requests simultaneously, leveraging the processing power of each GPU to improve throughput.
*** These values may be doubled when multiple replicas are configured
**** These pods require GPU nodes for operation
Rayman is the neural translation service on Ray (Ray Serve / KubeRay). It runs on a single GPU by default; the neural v4.0 pipeline that provides optional Uzbek and Chechen language support (replacing the former Emma model) requires one additional GPU. vCPU and memory ranges reflect the combined Ray head, application, and model worker groups.
n/a marked services have no specified limit in the configuration and can use available resources on the node. Services marked with n/a for both min and max have no explicit resource specifications defined in the helm charts and will use default values.