Skip to content
Xinyuanyi

Solutions

Inference-Stack Software Development

Software development

Updated

The problem

Once the hardware is in place, software is usually what stalls the project: the upstream framework does not support your card, the cache library has a defect under your load, or nobody has adapted a new model type.

Our approach

We change the inference stack at source level and hand the changes over as they are: the patch, the orchestration scripts and the raw data are all in R8R8.

Key points and sources

  • Upstream-grade engineering already demonstrated: ROCm builds of vLLM / LMCache, the parallel-read patch, a GDS adaptation layer and fs:// defect isolationR1R8
  • Fast validation of new requirements: AI video-generation pipelines (ComfyUI / LTX-Video already running)R6R7, private inference appliances and more
  • Developer resources: about 10,000 experienced software developers (the company's own figure, open to due-diligence checks and not used as evidence)
  • University cooperation: a partnership with Beijing Information Science and Technology University lets student developers, on the order of ten thousand by the university's own figure, join the ROCm ecosystem through joint courses and open-source practice

Related test reports

Test jointly first, decide afterwards

Every engagement starts with a gated joint test of about 10 weeks. Four gates are passed in sequence; if one is missed, the project stops there, so you never pay for a benefit that was not demonstrated.

  1. G1Week 2

    Delivery acceptance

    All materials delivered and inspected; every array passes its power-on self-test with all 24 drives recognized.

  2. G2Week 4

    Single-node baseline

    The single-node 8-GPU inference baseline is reproduced within ±10% of the R1 figures; a local stress test of one array reaches 83% line efficiency against the measured anchor.

  3. G3Week 7

    Main joint-test gate

    KV tiering must deliver both a TTFT reduction of ≥25% and a throughput gain inside the measured +29–40% band; with 8 nodes sharing one array, read-back bandwidth approaches the NIC ceiling.

  4. G4Week 10

    Stability and sign-off

    72 hours of continuous load without interruption; single-drive and single-link fault injection stays invisible to the workload; a signed joint-test report is issued.

Other solutions

Test jointly first, decide afterwards

Test jointly first, decide afterwards

Every engagement starts with a gated joint test of about 10 weeks. Four gates are passed in sequence; if one is missed, the project stops there, so you never pay for a benefit that was not demonstrated.

Contact
Wang Limin
Phone
+86 131 6181 8898
Email
mingxin@agentmail.to

The inbox is monitored and triaged by AI around the clock