CaraML Docs
CaraML Homepage
  • Introduction
    • What is CaraML?
    • Architecture
      • Feature Store Architecture
      • Models Architecture
      • Routers Architecture
      • Experiments Architecture
      • Pipelines Architecture
    • Core Concepts
      • Models Concepts
      • Router Concepts
      • Experiment Concepts
  • User guides
    • Projects
      • Create a project
      • Managing secrets
    • Feature Store
    • Models
      • Create a Model
        • Custom Model
      • Deploy a Model
        • Deploying a Model Version
        • Severing a Model Version
        • Configuring Transformer
          • Standard Transformer
            • Standard Transformer Expressions
            • Standard Transformer UPI
          • Custom Transformer
        • Redeploying a Model Version
      • Deleting a Model
      • Configuring Alerts
      • Batch Prediction
      • Model Schema
      • Model Observability
    • Routers
      • Creating a Router
        • Configure general settings
        • Configure routes
        • Configure traffic rules
        • Configure autoscaling
        • Configure experiment engine
        • Configure enricher
        • Configure ensembler
        • Configure logging
      • Viewing Routers
        • Configuration
        • History
        • Logs
        • More actions
      • Edit Routers
      • Monitoring router
        • Monitor Router Performance
        • Configure Alerts
      • Undeploying Router
      • Redeploying Router
        • Redeploy undeployed router
        • Redeploy version from history
        • Redeploy version from version details page
      • Deleting Router
        • Deleting router versions
        • Deleting router versions from details page
        • Deleting routers
      • Deleting Emsemblers
        • Delete an Ensembler without related entity
        • Delete an Ensembler with active entities
        • Delete an Ensembler with inactive entities
    • Experiments
      • View Experiment Settings
      • Modify Experiment Settings
      • Creating Experiments
      • Viewing Experiments
      • Modifying Experiments
      • Running Experiments
      • Monitoring Experiments
      • Creating Treatments
      • Viewing Treatments
      • Modifying Treatments
      • Creating Segments
      • Viewing Segments
      • Modifying Segments
      • Creating Custom Segmenters
      • Viewing Custom Segmenters
      • Modifying Custom Segmenters
    • Pipelines
  • Tutorial and Examples
    • Model Sample Notebooks
      • Deploy Standard Models
      • Deploy PyFunc Model
      • Using Transformers
      • Run Batch Prediction Job
      • Others examples on Models
    • Router Examples
    • Feature Store Examples
    • Pipeline Examples
    • Performing load test in CaraML
    • Best practice for CaraML
  • CaraML SDK
    • Feature Store SDK
    • Models SDK
    • Routers SDK
    • Pipeline SDK
  • Troubleshooting and FAQs
    • CaraML System FAQ
    • Models FAQ
      • System Limitations
      • Troubleshooting Deployment Errors
      • E2E Test
    • Routers FAQ
    • Experiments FAQ
    • Feature Store FAQ
    • Pipelines FAQ
    • CaraML Error Messages
  • Deployment Guide
    • Deploying CaraML
      • Local Development
    • Monitoring and alerting
      • Configure a monitoring backend
      • Configure an alerting backend
    • Prerequisites and Dependencies
    • System Benchmark results
    • Experiment Treatment Service
  • Release Notes
    • CaraML Release Notes
Powered by GitBook
On this page
  • Project
  • Project Name
  • Model
  • Model Name
  • Model Deployment
  • Resources
  • Autoscaling Policy
  • Autoscaling
  • Scale Down to Zero
  • Logs
  • Log History
  1. Troubleshooting and FAQs
  2. Models FAQ

System Limitations

This article is an aggregation of the limits imposed on various components of the Merlin platform.

Project

Project Name

A project name can only contain letters a-z (lowercase), numbers 0-9 and the dash - symbol. The maximum length of a project name is 50 characters.

An example of a valid project name would be gojek-project-01.

Model

Model Name

A model name can only contain letters a-z (lowercase), numbers 0-9 and the dash - symbol. The maximum length of a model name is 25 characters.

An example of a valid model name would be gojek-model-01.

Model Deployment

The maximum number of model versions that can be deployed in an environment is 2 per model.

Resources

The maximum amount of CPU cores that can be allocated to a model is 4.

The maximum amount of memory that can be allocated to a model is 8GB.

Autoscaling Policy

Autoscaling

Autoscaling is enabled for both staging and production environment. User can set minimum and maximum number of replica during deployment.

Scale Down to Zero

"Scaling down to zero" is a feature in Merlin, which automatically reduces the number of model deployments to zero when they haven't received any traffic for 10 minutes. To make the model available again, it must receive HTTP traffic, which triggers a scale-up.

This feature is only applicable when your autoscaling policy is set to either RPS or Concurrency."

Note that, to utilise this feature, the minimum replicas for the deployment should be set to 0.

Logs

Log History

Users can only view the logs that are still in the model’s container. Link to the associated Stackdriver dashboard is provided in the log page to access past log.

PreviousModels FAQNextTroubleshooting Deployment Errors

Last updated 1 year ago