scriptoriumadmin/supermemory
1
0
Fork 0
mirror of https://github.com/supermemoryai/supermemory.git synced 2026-10-01 02:01:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs(self-hosting): document database snapshots, dirty tracking, and write-burst behavior (#1413)

Browse source
This commit is contained in:
Aditya kumar singh 2026-09-20 02:16:18 +05:30
parent c927c98f2c
commit 9ba11a0374
1 changed files with 14 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
apps/docs/self-hosting/configuration.mdx
View file

@ -57,9 +57,21 @@ OPENAI_MODEL=gpt-oss:20b
| `OPENAI_FAST_MODEL` | Override for fast/light tasks | `OPENAI_MODEL` |
| `OPENAI_TEXT_MODEL` | Override for heavier text tasks | `OPENAI_MODEL` |
## File storage
## Storage & persistence
### File storage
Uploaded files (PDFs, images) are stored on local disk inside `$SUPERMEMORY_DATA_DIR` and served by the server at `/files/:key`.
### Database snapshots & resource usage
The self-hosted server persists its embedded relational database and vector indices as an encrypted snapshot container (`$SUPERMEMORY_DATA_DIR/data` with an `SMD1` header):
- **Dirty-tracked snapshots (`v0.0.7+`):** The server checks for pending writes on an internal timer. If no documents, memories, or metadata changed since the last snapshot, the dump is skipped completely, keeping idle CPU near 0%.
- **Streaming encryption:** Encryption streams directly to disk during snapshot writes to avoid double-buffering the raw unencrypted dump in RAM.
- **Write-activity bursts:** When new documents are being ingested or edited, the server writes dirty changes on its snapshot cycle. For larger stores (>100 MB), disk writes and CPU will spike briefly during active ingestion until the queue drains.
- **Graceful shutdown:** On `SIGINT` or `SIGTERM`, any pending dirty changes are flushed to disk before the process exits so no queued writes are lost.
Nothing to configure. Uploaded files (PDFs, images) are stored on local disk inside `$SUPERMEMORY_DATA_DIR` and served by the server at `/files/:key`.
## Embeddings