What SK hynix reported
In an October 16, 2026 report from OCP Global Summit, SK hynix described demonstrations of CXL pooled memory and its Memory Centric AI Rack System, or MARS. The company presented a second-generation, 256GB CMM-DDR5 product based on CXL 3.2 and described proof-of-concept work with NAVER Cloud involving shared KV caches and embeddings. Read SK hynix’s report.
The attraction of pooling is the ability to allocate memory capacity across multiple hosts rather than treating every server’s allocation as an isolated resource. SK hynix also described demonstrations involving reuse of AI inference data. These are manufacturer-reported demonstrations, not Ocitech benchmarks or evidence of broad production availability.
The useful procurement question is what a supported implementation would deliver in your environment. A successful demonstration can justify an evaluation without establishing that an unfamiliar architecture is ready for a particular production service.
Start with a problem you can measure
Before asking for a proposal, identify the current constraint. Record whether the service is limited by available capacity, response time, data movement or another measured factor. A project described simply as “more memory for AI” makes it difficult to judge whether a proposed change solves the actual problem.
Build a baseline from a representative workload. Keep the data set, request mix and service targets consistent when comparing a candidate system. Include busy periods and concurrent jobs rather than evaluating only an isolated demonstration with favorable conditions.
Three questions for a CXL pilot
Compare workload completion, response-time targets and usable capacity against a documented baseline.
Test monitoring, allocation policies, isolation, recovery and maintenance procedures.
Confirm the supported configuration, software, delivery terms and complete system cost.
Define acceptance criteria before the pilot begins. Specify the required result, the measurement method and who signs off. If a supplier reports an improvement, ask what changed between the baseline and the proposed configuration, including software and total installed resources.
Ask how the system behaves when conditions change
A purchasing discussion should cover more than a best-case performance chart. Ask the supplier to explain resource allocation when several workloads compete, how access is isolated and what monitoring reveals when an application misses its target.
Include failure and recovery in the evaluation plan. Request a documented account of what happens when a component becomes unavailable, who receives the alert and which services require intervention. Those questions define what the operations team must support; they do not presume a particular failure behavior for every CXL implementation.
Request a complete compatibility statement covering the hosts, memory devices, interconnect equipment where required, firmware and software stack. Identify which organization owns support across those boundaries. A list of individually capable components is less useful than a tested configuration with a clear escalation path.
Compare complete proposals
Price the configuration that would actually be deployed. Include software licensing where applicable, integration, support and the effort needed to run the new environment. Compare that total with the cost of meeting the same workload requirement using an approved existing approach.
Keep product status explicit in every quote. Ask whether the offer concerns evaluation hardware or an orderable production configuration, and obtain written delivery and support commitments. The announcement alone should not become a delivery date in a project plan.
For teams managing surplus RDIMMs, this development is not an appraisal of existing inventory. Continue identifying stock by full part number, condition and quantity, and use current offers for the actual lot when making a disposal decision. A new architecture does not by itself establish the resale value of the hardware already on your shelf.
Use the demonstration to shape a better evaluation. Use the evaluation to decide whether the system belongs in production.
Prepared October 16, 2026 using SK hynix’s October 16 OCP report. Product and demonstration details are attributed to the manufacturer. The pilot and procurement recommendations are Ocitech’s analysis; no independent performance results, pricing forecasts or general-availability dates are asserted.