Alibaba Cloud Media and Entertainment China Translated from Chinese

Rokid

Application Refactoring

Rokid's 3D mapping and AR-experience pipeline needed far more GPU elasticity than a small set of ECS GPU machines could provide. Long videos took hours to process serially, engineers had to request and release ECI capacity manually, and asynchronous step orchestration plus weak monitoring made failures and cost leaks hard to control.

1 hour of video originally took about 3 hours on a single ECS GPU machine
GPU utilization can reach 60% to nearly 100% during active processing
compute cost for the 3D-mapping module dropped about 40%
products are used in 80+ countries and regions

Reported impact

Business outcome

Rokid shortened job completion times, lowered GPU spend for offline processing, and improved observability across a complex spatial-computing workflow. The company can now use serverless GPU elasticity for batch processing while reserving fixed capacity only where real-time AR latency truly demands it.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Rokid refactored its spatial-computing pipeline around Alibaba Cloud Function Compute so the GPU-intensive 3D-mapping portion of the workflow could run as a true serverless service. The company packages its processing logic into container images and lets Function Compute allocate GPU resources on demand, which removes the manual process of requesting, operating, and releasing ECI instances for each job. Function Compute's asynchronous system also lets Rokid chain multi-step 3D-modeling tasks so the output of one stage automatically triggers the next instead of relying on a separate coordination service. Built-in metrics, alerts, traces, and logs improve observability across the whole processing lifecycle, while warm-resource capabilities and reserved instances reduce the latency of subsequent invocations. For the real-time scene-experience module, where sub-second response is mandatory, Rokid still keeps ECI capacity scheduled ahead of peak times, giving the company a split architecture optimized for both offline GPU throughput and real-time AR response.

Data flow

Captured venue video and scene assets are split into asynchronous processing stages and sent to Function Compute GPU jobs launched from container images. Each stage emits outputs that trigger the next step in the 3D-modeling pipeline, while the real-time AR positioning service is served separately from scheduled ECI capacity.

Solution architecture

4 components · 2 layers
  1. Compute
    • Function Compute Runs Rokid's GPU-intensive 3D-mapping and asynchronous processing steps on demand.
    • Reserved GPU instances Keep pre-initialized runtime state available for faster follow-on requests.
    • Elastic Container Instance (ECI) Handles the real-time scene-experience module that requires consistently sub-second response.
  2. Storage
    • Container Registry (ACR) Stores the images used to launch Function Compute GPU workloads.

Architecture clues

  • Function Compute handles step chaining through its async system, eliminating an extra orchestration layer for batch GPU jobs.
  • Reserved instances are used to reduce subsequent startup time without returning to permanently provisioned GPU servers.
  • Rokid splits offline 3D modeling and real-time positioning into different runtime patterns instead of forcing both into one service model.

Evidence from the source

Function Compute solved the need to request and release ECI manually, handled asynchronous step chaining, and added metrics, alarms, traces, and logs for full lifecycle operations. (original: 函数计算会根据请求流量,动态的拉起与请求量匹配的后端 GPU 算力资源... 通过函数计算的异步系统,在一个步骤的任务完成后,可以自动触发下一个任务... 内置了指标监控、异常告警、链路追踪、调用日志。)
Rokid said one hour of captured video could take about three hours to process on a single ECS GPU machine before the redesign. (original: 通常一个 1 小时的视频资料,通过一台 ECS GPU 机器处理需要耗费约 3 小时。)
Since the February 2023 launch, the 3D-mapping module cut compute cost by about 40%, while GPU utilization during active work can reach 60% to nearly 100%. (original: 该改造自 2023 年 2 月上线以来... 算力成本降低了 40%... GPU 计算利用率可以达到 60% 甚至接近 100%。)
Transparency Evidence & methodology 95/100 reference value · 88% confidence · 1 source

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 value95/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
    3 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence88%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference 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

    阿里云Serverless服务助力Rokid人机交互平台实现降本增效_人工智能_阿里云客户案例

    First-party
    https://www.aliyun.com/customer-stories/ai-2024-rokid
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Published on source page Jun 10, 2024 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.