Repository navigation
docs: DDR3 network-RAM tier (parked possibility) - #95
Merged
Merged
Conversation
Add a research spec for reusing an old DDR3 server as a volatile far-RAM Cache-Me-Outside host and optional NVMe-over-TCP RAM disk. Link it from the docs index, the roadmap, and the feature plan under parked / future ideas. Not a shipping feature and not a commitment to build.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a parked research spec for using an old DDR3 server as a volatile far-RAM Cache-Me-Outside host, and optionally as an NVMe-over-TCP RAM disk. This came out of looking at Astera Labs Leo 2 CXL expanders; a DDR3 CXL card is not a practical build, so the document records the network-RAM alternative in enough detail to set one up later.
Documentation only. No code, no deploy, no hardware purchase, and no commitment to un-park the work.
Changes
docs/research/ddr3-network-ram-tier.md(status: PARKED / possibility).docs/cache-me-outside/README.md,roadmap.md, andrea-feature-plan.md.Why this shape
The operator docs already describe hosts, near cache, hybrid flash spill, TTL segments, the console, and the SDKs. The spec slots far-RAM in as a volatile host tier between local RAM and SSD, with a separate block-device runbook that is adjacent infrastructure, not a RESP feature.