Alibaba Cloud Healthcare China Translated from Chinese

Deep Potential (深势科技)

Deep Potential needed infrastructure for AI-for-science workloads whose compute demand could spike to hundreds of thousands of cores and whose data path had to support heterogeneous compute pools, hot small files, rapid loading, and quota management. Its Bohrium and Hermite platforms needed storage and scheduling patterns that could keep scientific AI jobs fast and economical even under extreme elasticity.

drug screening and optimization can be shortened from years to months or weeks
peak resource demand can reach hundreds of thousands of cores
phd and postdoc staff account for more than 35% of the company

Reported impact

Business outcome

Alibaba Cloud helped Deep Potential turn AI-for-science infrastructure into a production system for industrial and biomedical R&D. The platform can handle hundreds of thousands of cores at peak, support cross-discipline data pooling, and shorten drug-screening and optimization cycles from years to months or even weeks while keeping storage and compute spending under tighter control.

  • Cost Reduction
  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Deep Potential and Alibaba Cloud designed a layered data infrastructure for AI-driven scientific computing and drug design. Near the compute tier, Fluid turns high-speed media inside the cluster into a logical cache layer so model files and data can be loaded faster and images can be pulled quickly enough to launch Pods in seconds. Above that, a general-purpose NAS layer provides shared read or write acceleration for many clusters and helps absorb hotspots caused by huge numbers of small files. For long-term retention, multi-tier OSS stores model files, checkpoints, and datasets economically while still supporting cross-region loading through Alibaba Cloud's global network. Those layers back Deep Potential's Bohrium research cloud and Hermite drug-design platform, allowing the company to pool data across heterogeneous compute, schedule large elastic jobs, and move from experiment-heavy workflows toward model-driven scientific discovery.

Data flow

Scientific datasets, model files, and checkpoints are held in OSS, accelerated into NAS for multi-cluster sharing, and cached close to compute by Fluid when jobs are launched on ACK, ACS, and ECS. Those layers feed Bohrium and Hermite workflows so large-scale simulation, training, and drug-design tasks can load data quickly and schedule elastic compute resources efficiently.

Solution architecture

6 components · 3 layers
  1. Compute
    • Container Compute Service (ACS) Adds elastic container compute capacity for scientific workloads that need rapid scale-out.
    • Elastic Compute Service (ECS) Provides additional compute resources that work with the broader AI-for-science infrastructure.
  2. Storage
    • Fluid Creates the near-compute logical cache layer that speeds data access and image pulls for scientific AI jobs.
    • NAS Provides shared accelerated storage for many clusters and mitigates hot-small-file performance issues.
    • Object Storage Service (OSS) Stores model files, checkpoints, and datasets as the long-term low-cost data layer.
  3. Orchestration
    • Container Service for Kubernetes (ACK) Runs containerized AI-for-science workloads that consume the layered storage design.

Architecture clues

  • Elastic compute and data pooling are designed for heterogeneous AI-for-science workloads rather than one fixed model pipeline.
  • Pod startup speed is treated as a scientific productivity bottleneck, so image caching is part of the data design.
  • The infrastructure deliberately splits storage into near-compute cache, shared acceleration, and long-term archival layers.
  • The same storage design supports both AI model artifacts and domain datasets such as checkpoints and scientific corpora.

Evidence from the source

Deep Potential layered the infrastructure into a near-compute cache with Fluid, a shared acceleration layer with NAS, and a long-term storage layer with OSS. (original: 数据缓存层... 使用阿里云 Fluid... 共享加速层... 采用阿里云通用型 NAS 方案... 长期存储层... 采用阿里云多级 OSS 对象存储方案。)
Deep Potential said its scientific-computing workloads can demand hundreds of thousands of cores and must provision compute and data resources in sub-minute or even second-level windows. (original: 科学计算任务对资源的需求具有极致弹性,峰值资源需求可达数十万核,需要在亚分钟级甚至秒级完成计算和数据资源的准备。)
The AI-for-science workflow needed heterogeneous compute, pooled data, low-latency handling of hot small files, and unified dataset management. (original: AI for Science 全链路涉及多种异构算力和数据池化的需求... 需要对热点小文件实现低延迟加速,并且在高频弹性任务中实现数据的极速加载和统一的数据集管理。)
With this platform, users can reduce drug screening and optimization work from years to months or even weeks. (original: 将原本需要数年才能完成的药物筛选和优化工作,用更大规模的算力协同调度缩短至几个月甚至几周。)
Transparency Evidence & methodology 90/100 reference value · 95% 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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence95%
  • 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 evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/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

    AI 变革药物研发:深势科技基于阿里云存储服务的云原生实践之路

    First-party
    https://www.aliyun.com/customer-stories/internet-and-info-tech-2025-dp-tec
    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 Apr 24, 2025 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.