Storage Sync

Synchronize memories between Turso (durable) and redb (cache) storage layers.

When to Sync

1. On startup - After system initialization
2. Periodic - Scheduled background sync
3. Cache staleness - When redb appears outdated
4. Recovery - After storage failures
5. Manual trigger - When explicitly requested

Sync Process

1. Check connection health:

``rust tursoclient.ping().await?; redbenv.check_integrity()?; ``

1. Fetch latest from Turso:

``rust let episodes = tursoclient .query("SELECT * FROM episodes ORDER BY timestamp DESC LIMIT ?") .bind(maxepisodes_cache) .await?; ``

1. Update redb cache:

``rust tokio::task::spawnblocking(move || { let writetxn = redb.beginwrite()?; let mut table = writetxn.opentable(EPISODESTABLE)?; for episode in episodes { table.insert(episode.id.asbytes(), episode.tobytes())?; } write_txn.commit()?; }); ``

1. Sync patterns and embeddings if enabled

Configuration

pub struct SyncConfig {
    pub max_episodes_cache: usize,  // Default: 1000
    pub batch_size: usize,          // Default: 100
    pub sync_patterns: bool,        // Default: true
    pub sync_embeddings: bool,      // Default: true
}

Error Handling

Performance Tips

• Batch small operations
• Incremental sync (only changes)
• Parallel fetch with Tokio
• Write-ahead preparation

Validation

After sync, verify:

• Episode count matches
• Latest episodes present
• Pattern counts consistent
• No orphaned embeddings

Troubleshooting