Slides演示文稿
Master gridThe master grid
Header, title and footer hold their positions on every slide, so nothing jumps.
标题首行落在基线上The first line of every title sits on the baseline
正文不小于 28 px,本母版使用 32 px。Body type is 28 px or larger; this master uses 32 px.
每页不超过 6 条要点,每条不超过 2 行。Six bullets at most, two lines each.
数字带单位,并注明来源与统计日期。Numbers carry a unit, a source and a date.
Type sizes
At 1920 × 1080 · 1u = 10.8 px| Role | Typeface | Size | u |
|---|---|---|---|
| Cover title | Archivo 125% · ExtraBold | 151 px | 14u |
| Section number | Archivo 125% · ExtraBold | 432 px | 40u |
| Statement | Archivo 125% · Chinese sans Bold | 162–173 px | 15–16u |
| Slide title | Archivo 112% · Bold; Chinese sans Bold | 70 px | 6.5u |
| Subhead | Archivo 112% · Bold | 46 px | 4.25u |
| Body | Geist · Regular / Medium | 32 px, never below 28 px | 3u |
| Code | Geist Mono · Regular | 30 px | 2.75u |
| Labels, footer, source line | Geist Mono · Medium · caps | 22 px | 2u |
LayoutsLayouts
In the order of a complete talk; slide numbers match the agenda.
Present all 18 slides full screen
← → or Space to move · Esc to exit
RustFS 1.0
面向 AI 时代的对象存储Object storage for the AI era
RustFS 1.0
面向 AI 时代的对象存储Object storage for the AI era
议程Agenda
4 个部分parts · 18 页slides- 01背景Context对象存储面临的变化与 RustFS 的定位What is changing in object storage, and where RustFS fits页pp. 05–07
- 02能力与采用Capabilities纠删码、位腐烂保护、自愈与社区规模Erasure coding, bitrot protection, healing and adoption页pp. 08–10
- 03架构与部署Architecture从 S3 请求到磁盘,以及三条命令完成部署From S3 request to drive, and a three-command deployment页pp. 11–13
- 04原则与路线Principles & roadmap设计原则、里程碑与团队Design principles, milestones and the team页pp. 14–17
背景Context
对象存储面临的变化与 RustFS 的定位What is changing in object storage, and where RustFS fits
页pp. 05–07AI 时代的基建,
从每一个字节算起。AI infrastructure,
accounted for byte by byte.
单机起步,按池扩展Start on one machine, grow by pools
- 单节点、单块盘即可启动,适用于开发与边缘场景。One node, one drive: enough for development and the edge.
- 生产部署将数据块与校验块分布到多节点、多块盘。Production spreads data and parity across many drives.
- 新增服务器池即可扩容;已有数据保留在原池中。Add server pools to grow; existing data stays where it is.
- 兼容 S3 的 API 可直接接入现有 SDK 与命令行工具。The S3-compatible API works with existing SDKs and CLIs.
数据持续增长,掌控不能减少Data keeps growing; control must not shrink
数据保持完整的三重机制Three mechanisms keep data whole
纠删码Erasure coding
对象被切分为 k 个数据块与 m 个校验块,写入纠删集中的不同磁盘。任意 m 块盘故障,数据仍可读取。Each object is split into k data and m parity shards on separate drives of an erasure set. Data stays readable with any m drives lost.
位腐烂保护Bitrot protection
每个分片写入时计算校验和,读取时重新校验。静默损坏的分片会被识别,不作为正确数据返回。Every shard is checksummed on write and verified on read. A silently corrupted shard is detected and never served as good data.
自愈Healing
磁盘更换或分片损坏后,后台修复从其余分片重建缺失的数据,无需人工逐个恢复对象。After a drive is replaced or a shard is damaged, background healing rebuilds the missing data from the remaining shards.
社区与采用Community and adoption
- 34,869
- GitHub StarsGitHub Stars
- 15.15M
- Docker 拉取 · 15,154,618Docker pulls · 15,154,618
- 7,094
- 代码提交Commits
数据来源:RustFS 官方网站。统计日期:2026-10-14。Source: the official RustFS website. As of 2026-10-14.
读取吞吐量随对象大小变化Read throughput by object size
示例数据,仅用于展示版式。正式图表须注明硬件、版本、并发数与测试日期。Sample data, for layout only. Real charts state hardware, versions, concurrency and test date.
从 S3 请求到磁盘From S3 request to drive
三条命令
运行 RustFSRun RustFS in three commands
- S3 API
- localhost:9000
- 控制台Console
- localhost:9001
- 容器以 UID 10001 运行,数据与日志目录须对该用户可写。The container runs as UID 10001; the data and log directories must be writable by that user.
# 数据目录须对 UID 10001 可写# data dirs must be writable by UID 10001 $ mkdir -p data logs $ chown -R 10001:10001 data logs $ docker run -d -p 9000:9000 -p 9001:9001 \ -v $(pwd)/data:/data \ -v $(pwd)/logs:/logs \ rustfs/rustfs:latest # S3 API http://localhost:9000 # Console http://localhost:9001
选型对照:只比可验证的事实Comparison: verifiable facts only
仅列可核实的类别。具体产品的对应信息以其官方文档为准。Only verifiable categories are listed. For a specific product, refer to its official documentation.
RustFS 设计原则RustFS design principles精确胜过响亮。Exact over loud.
用真实数字代替形容词。数字须标注单位、来源与统计日期;
性能数据只使用同环境实测,并注明测试条件。Replace adjectives with real numbers. Every figure carries a unit, a source and a date; performance figures come only from like-for-like runs, with the conditions stated.
里程碑Milestones
演讲者与团队Speakers and team
谢谢Thank you
演讲者姓名 · 邮箱或社交账号Speaker name · email or handle
PowerPoint & KeynoteBuilding in PowerPoint and Keynote
Every deck starts from a master that matches this page; never copy slides from older decks.
Fonts
SIL Open Font License 1.1| Role | Typeface | Source | Fallback |
|---|---|---|---|
| Covers, section numbers, statements | Archivo Expanded · ExtraBold | Google Fonts · OFL | Arial Bold |
| Slide titles, subheads | Archivo SemiExpanded · Bold | Google Fonts · OFL | Arial Bold |
| Body | Geist · Regular / Medium | Google Fonts · OFL | Arial |
| Labels, data, code | Geist Mono · Regular / Medium | Google Fonts · OFL | Consolas |
| Chinese | HarmonyOS Sans SC or Source Han Sans SC | HarmonyOS site · Source Han Sans OFL | Microsoft YaHei |
Theme colours
PowerPoint: Design → Variants → Colours → Customise ColoursSize, guides and type conversion
PowerPoint widescreen: 1 pt = 2 px| Item | Template (px) | Keynote | PowerPoint |
|---|---|---|---|
| Slide size | 1920 × 1080 | Wide 1920 × 1080 | 13.333 × 7.5 in · 33.867 × 19.05 cm |
| Margin guides | 96 | 96 pt | 0.667 in · 1.693 cm |
| 12 columns · width / gutter | 122 / 24 | 122 / 24 pt | 0.847 / 0.167 in |
| Title zone top | 216 | 216 pt | 1.5 in · 3.81 cm |
| Cover title | 151 | 151 pt | 76 pt |
| Slide title | 70 | 70 pt | 35 pt |
| Subhead | 46 | 46 pt | 23 pt |
| Body (minimum) | 32 (28) | 32 (28) pt | 16 (14) pt |
| Labels, footer, source line | 22 | 22 pt | 11 pt |
Master layouts
Layout names are always in English| Master layout name | PowerPoint base layout | Placeholders |
|---|---|---|
| 01 Cover – Ink | Title Slide | Title, subtitle, speaker, event, date |
| 02 Cover – Signal | Title Slide | Title, subtitle, speaker, event, date |
| 03 Agenda | Title and Content | Title, numbered list |
| 04 Section | Section Header | Number, section name, description |
| 05 Statement | Title Only | Statement |
| 06 Title + Bullets + Visual | Two Content | Title, bullets (7 cols), visual (5 cols) |
| 07 Two Columns | Comparison | Title, two headings, two bodies |
| 08 Three Features | Title Only | Title, three icon and text groups |
| 09 Big Numbers | Title Only | Title, lead figure, three figures, source line |
| 10 Chart | Title and Content | Title, chart, source line |
| 11 Diagram | Title Only | Title, diagram area |
| 12 Code | Two Content | Title, notes, code box (mono) |
| 13 Table | Title and Content | Title, table, source line |
| 14 Quote | Title Only | Quote, explanation, attribution |
| 15 Timeline | Title Only | Title, four milestones |
| 16 Speakers | Title Only | Title, four picture placeholders with text |
| 17 Picture + Caption | Picture with Caption | Picture (8 cols), figure number, title, caption |
| 18 Closing | Blank | Thanks, contact, QR code, links |
Export and delivery
- PDF: confirm in the document properties that every font is embedded.
- PPTX: turn on Embed fonts in the file, with all characters.
- Keynote files carry no fonts: send a PDF or confirm they are installed.
- If the number field cannot produce “07 / 18”, fill it in once the deck is final.
Do & Don'tBefore you present
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…
- Erasure coding, bitrot protection, healing, versioning, Object Lock, replication, lifecycle and tiering…