Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. Tuning and Sizing Guidelines for Data Engineering Integration (10.4.x)

Tuning and Sizing Guidelines for Data Engineering Integration (10.4.x)

Tuning and Sizing Guidelines for Data Engineering Integration (10.4.x)

Model Repository Service

Model Repository Service

You can tune the maximum heap size for the separate Model Repository Service instances that you use for design and for monitoring.
The following table lists the guidelines to tune heap sizes:
Parameter
Sandbox Deployment
Basic Deployment
Standard Deployment
Advanced Deployment
Max heap size -- Design Model repository
1 GB
1 GB
2 GB
4 GB
Max heap size -- Monitoring Model repository
1 GB
1 GB
2 GB
4 GB
Heap size requirements on the Model Repository Service are primarily driven by the number of simultaneous save, fetch, and delete operations and the number of concurrent mapping executions. Model Repository Service actions, such as application deploy, redeploy, import, and export, also affect the heap size requirements and the efficiency of design-time operations.
If you implement CI/CD, use a maximum heap size of 8 GB on the design Model repository to scale CI/CD operations for up to 1,000 objects.

Additional Guidelines

Consider the following additional guidelines for the Model Repository Service:
  • Create a separate Model Repository Service for persisting monitoring statistics.
  • Schedule a periodic purge of monitoring statistics and retain only the required statistics.
  • When you upgrade the Model Repository Service, the minimum JVM heap requirement is 4 GB.
When you create a Model Repository Service for monitoring, you must size your database to account for the growth of monitoring statistics. Consider the rate of growth in monitoring statistics when you decide statistics retention policies and schedule purge policies for the Model Repository Service. For instance, the monitoring statistics for 1,000 mappings require around 200 MB. Retaining the statistics for 30 days with a daily workload of 1,000 mappings requires around 6 GB of tablespace on the database.

0 COMMENTS

We’d like to hear from you!