mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-14 06:36:54 +00:00
Jack YeandClaude Sonnet 5
dfbf682cb5
## Summary Every Mermaid diagram now renders in the brand palette, with separate light and dark variants that switch with the site's theme toggle. Default node styling stays neutral; one accent color marks each diagram's actual subject, chosen per diagram. A couple of diagrams changed orientation where their old layout was too wide to read comfortably. Companion change in lancedb/sophon uses the same colors and pattern. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_018PXMCbRH6i5w47TsjeEUMT Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
103 lines
4.5 KiB
Plaintext
103 lines
4.5 KiB
Plaintext
---
|
|
title: "Training Cache"
|
|
sidebarTitle: "Training Cache"
|
|
description: "Connect the PyTorch data loader to LanceDB Enterprise and training reads automatically benefit from the plan executor's data page cache."
|
|
icon: "gauge-high"
|
|
keywords: ["training", "dataloader", "cache", "data page cache", "enterprise", "epoch"]
|
|
availability:
|
|
embedded: unavailable
|
|
enterprise: available
|
|
---
|
|
|
|
The [PyTorch data loader](/training/data-loading) reads training data the
|
|
same way any other query does -- there is no training-specific read path.
|
|
Point `StreamingDataset` or a `DataLoader` at a table opened through an
|
|
Enterprise connection instead of a local one, and every read it makes
|
|
flows through the same [plan executors](/enterprise/data-page-cache) that
|
|
serve every other query, with the same data page cache in front of object
|
|
storage. No training-specific configuration turns this on; it's a
|
|
consequence of connecting to Enterprise at all.
|
|
|
|
<div className="hidden dark:block">
|
|
|
|
```mermaid
|
|
%%{init: {"theme": "base", "themeVariables": {
|
|
"background": "#171513", "primaryColor": "#1e1b19", "primaryTextColor": "#f4ebe8",
|
|
"primaryBorderColor": "#4c443f", "lineColor": "#847770", "textColor": "#f4ebe8",
|
|
"edgeLabelBackground": "#171513", "fontFamily": "Inter, sans-serif", "fontSize": "15px"
|
|
}}}%%
|
|
flowchart LR
|
|
DL["PyTorch DataLoader<br/>/ StreamingDataset"] --> T["Enterprise-connected table"]
|
|
T --> PE["Plan executor"]
|
|
PE --> C{"In data page cache?"}
|
|
C -->|hit| Fast["Served from memory<br/>or local disk"]
|
|
C -->|miss| O[("Object storage")]
|
|
O --> Fill["Fills the cache,<br/>served"]
|
|
classDef default fill:#1e1b19,stroke:#4c443f,stroke-width:1px,color:#f4ebe8
|
|
classDef accent fill:#2a1810,stroke:#ff734a,stroke-width:1.5px,color:#f4ebe8
|
|
class Fast accent
|
|
```
|
|
|
|
</div>
|
|
|
|
<div className="block dark:hidden">
|
|
|
|
```mermaid
|
|
%%{init: {"theme": "base", "themeVariables": {
|
|
"background": "#ffffff", "primaryColor": "#ffffff", "primaryTextColor": "#221d19",
|
|
"primaryBorderColor": "#ad9e95", "lineColor": "#6b625c", "textColor": "#221d19",
|
|
"edgeLabelBackground": "#ffffff", "fontFamily": "Inter, sans-serif", "fontSize": "15px"
|
|
}}}%%
|
|
flowchart LR
|
|
DL["PyTorch DataLoader<br/>/ StreamingDataset"] --> T["Enterprise-connected table"]
|
|
T --> PE["Plan executor"]
|
|
PE --> C{"In data page cache?"}
|
|
C -->|hit| Fast["Served from memory<br/>or local disk"]
|
|
C -->|miss| O[("Object storage")]
|
|
O --> Fill["Fills the cache,<br/>served"]
|
|
classDef default fill:#ffffff,stroke:#ad9e95,stroke-width:1px,color:#221d19
|
|
classDef accent fill:#fff1ec,stroke:#e8582d,stroke-width:1.5px,color:#221d19
|
|
class Fast accent
|
|
```
|
|
|
|
</div>
|
|
|
|
This covers the ordinary tabular columns a query reads -- the data page
|
|
cache's unit is a fixed-size page of table data. A [Blob v2](/management/table#managed-blobs)
|
|
column's payload is fetched through a separate range-request path keyed
|
|
to its own descriptor, not through this cache, so a training table mixing
|
|
plain feature columns with Blob v2 images or video gets this benefit only
|
|
for the former. A custom collate function or transform that does its own
|
|
file or network I/O -- decoding an image, say -- is also outside this
|
|
cache; only reads that go through the table query path benefit.
|
|
|
|
## Why this matters for training specifically {#why}
|
|
|
|
Training reads the same rows repeatedly: once per epoch, often for many
|
|
epochs. The first epoch's reads behave like any cold cache -- a miss per
|
|
page, each one filling the cache on the way. Every epoch after that reads
|
|
the same pages again, so a dataset that fits the cache's budget serves
|
|
almost entirely from memory or local disk after the first pass, instead of
|
|
re-reading object storage every epoch. A local-file or Embedded
|
|
connection has no equivalent remote cache to warm this way -- its
|
|
locality comes from whatever the local filesystem or OS page cache
|
|
already does.
|
|
|
|
[Cache Prewarm](/enterprise/cache-prewarm) extends this further: a plan
|
|
executor can warm its cache at startup, before training even begins,
|
|
instead of paying the first-epoch cold-cache cost during the run itself.
|
|
|
|
## What to read next {#next}
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="PyTorch Data Loader" icon="boxes-stacked" href="/training/data-loading">
|
|
Connecting a DataLoader to an Enterprise table.
|
|
</Card>
|
|
<Card title="Data Page Cache" icon="database" href="/enterprise/data-page-cache">
|
|
How the cache a training read benefits from actually works.
|
|
</Card>
|
|
<Card title="Cache Prewarm" icon="fire" href="/enterprise/cache-prewarm">
|
|
Warming the cache before the first epoch instead of during it.
|
|
</Card>
|
|
</CardGroup>
|