Alibaba Cloud Software / SaaS China Translated from Chinese

Moonshot AI (月之暗面)

Application Refactoring

Moonshot AI needed a more stable and elastic way to preprocess TB-scale multimodal training data for Kimi. Its self-managed Ray and Spark environment struggled with large-cluster stability, could not scale bursty short jobs efficiently, and lacked the job-level observability and priority controls needed by multiple internal teams sharing the same preprocessing estate.

anomaly-response speed improved 50%
burst-task resource utilization improved 3x
fault-location efficiency improved 60%
high-priority task SLA reached 99%+

Reported impact

Business outcome

Moonshot AI raised burst-task resource utilization 3x, cut overall compute cost by 45%, reached 99.95% stability for TB-scale single-job preprocessing, and improved observability so high-priority model-data jobs can be scheduled and troubleshot faster.

  • Cost Reduction
  • Productivity Improvement
  • Risk Reduction
  • Scalability

Solution

Moonshot AI rebuilt Kimi's data-preprocessing pipeline on Alibaba Cloud around Alibaba Cloud Container Service for Kubernetes (ACK) and managed Ray and Spark tooling. Text, image, audio, and video corpora are processed by Managed KubeRay and ack-spark-operator workloads inside ACK instead of self-maintained clusters. ACK schedules jobs across ECS capacity and Container Compute Service (ACS), including ACS BestEffort pools for short, fault-tolerant bursts, while Object Storage Service (OSS) provides the shared storage and recovery layer for datasets and event logs. Managed Service for Prometheus, Spark/Ray History Server, and Log Service (SLS) add job-level metrics, dashboards, and centralized logs so teams can watch progress, resource usage, and failures in real time. The result is a more elastic preprocessing platform that improves stability, lowers cost, and gives Moonshot tighter control over Kimi model-data workloads.

Data flow

Multimodal training data is written to OSS, then Spark and Ray jobs launched through ack-spark-operator and Managed KubeRay run on ACK across ECS and ACS capacity. Metrics flow into Prometheus, execution history and event logs are written back to OSS and History Server, and ECS and ACS pod logs are centralized in SLS so teams can monitor progress and tune job priority or capacity.

Solution architecture

9 components · 4 layers
  1. Compute
    • Container Compute Service (ACS) Supplies serverless container compute so Spark and Ray jobs can expand quickly when preprocessing demand spikes.
    • ACS BestEffort Provides lower-cost elastic capacity for short-lived, fault-tolerant preprocessing jobs.
  2. Storage
    • Object Storage Service (OSS) Stores large training datasets, versioned objects, and event logs that support the preprocessing pipeline.
    • Log Service (SLS) Centralizes engine and business logs from ECS and ACS pods for troubleshooting and analysis.
  3. Orchestration
    • Alibaba Cloud Container Service for Kubernetes (ACK) Provides the managed Kubernetes control plane that runs and scales Moonshot AI's Ray and Spark preprocessing workloads.
    • Managed KubeRay Runs RayCluster and RayJob workloads for large-model data preprocessing without requiring Moonshot AI to maintain KubeRay itself.
    • ack-spark-operator Submits and manages Spark preprocessing jobs on ACK through Kubernetes-native custom resources.
  4. Governance
    • Managed Service for Prometheus Collects metrics from Ray clusters so teams can monitor preprocessing health and performance.
    • Spark/Ray History Server Exposes job execution history and web dashboards backed by logs written to OSS.

Architecture clues

  • ACS BestEffort is reserved for short, fault-tolerant jobs where lower-cost elastic capacity is acceptable.
  • Moonshot AI runs Spark and Ray side by side on ACK instead of on self-built clusters.
  • OSS versioning and bucket-level traffic controls are used to protect recoverability and throughput.
  • Prometheus, History Server, and SLS provide the monitoring and logging plane for job-level observability.
  • The preprocessing estate handles text, image, audio, and video data for large-model training.

Evidence from the source

ACK's fully managed operations solved large-cluster stability issues and delivered extreme on-demand elasticity with diverse compute options. (original: 通过 ACK 的全托管免运维,解决了大规模集群的稳定性问题。同时充分发挥 ACK 在极致弹性和多样算力方面的关键能力,实现了任务的按需极致弹性伸缩。)
Moonshot AI needed cost-effective and elastic CPU and GPU capacity for model-data preprocessing so it could speed up Kimi's training iteration. (original: 月之暗面作为基础模型创业公司,为了加速大模型的训练迭代,在模型数据预处理方面,需要高性价比、弹性灵活的 CPU 和 GPU 算力满足模型迭代的业务需求。)
Moonshot AI used ACS BestEffort for many jobs, which both kept execution efficient and reduced compute cost. (original: 在部分任务场景中,月之暗面大量采用了 ACS BestEffort 算力,不仅确保了任务的高效执行,还有效地节省了计算成本。)
Under the original architecture, preprocessing ran on self-built Ray and Spark frameworks, but TB-scale jobs suffered from poor large-cluster stability. (original: 在用户原有的架构下,数据预处理任务均基于自建的 Ray 和 Spark 框架开展... 大规模 Spark/Ray 集群稳定性较差,难以保障 TB 级数据预处理任务的稳定执行。)
With the Alibaba Cloud architecture, single-task TB-scale processing stability reached 99.95%, burst-task resource utilization improved 3x, and overall compute cost fell 45%. (original: 单任务 TB 级数据处理稳定性达到 99.95%... 突发性任务资源利用率提升 3 倍,综合计算成本降低 45%。)
Transparency Evidence & methodology 100/100 reference value · 93% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    7 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence93%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Alibaba Cloud

    月之暗面 Kimi 大模型基于阿里云 ACK 实现海量数据预处理

    First-party
    https://www.aliyun.com/customer-stories/internet-and-info-tech-2025-moonshot
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. Moonshot AI

    Moonshot AI

    First-party
    https://www.moonshot.cn/about

    “联系地址 北京市海淀区知春路76号京东科技大厦1栋13层。”

    Source type
    Official company website
    Supports
    • Region

Date evidence

  • Published on source page Apr 9, 2025 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.