feat: implement always-adaptive caching with getCacheStats monitoring

Replaces lazy mode concept with always-adaptive caching strategy:

- Rename getLazyModeStats() → getCacheStats() with enhanced metrics
- Change lazyModeEnabled boolean → cachingStrategy enum ('preloaded' | 'on-demand')
- Update preloading threshold from 30% to 80% for better cache utilization
- Add comprehensive production monitoring and diagnostics
- Add memory detection for containers (Docker/K8s cgroups v1/v2)
- Add adaptive memory sizing from 2GB to 128GB+ systems

Breaking changes: None (backward compatible, deprecated lazy option ignored)

New APIs:
- getCacheStats(): Comprehensive cache performance statistics
- cachingStrategy field: Transparent strategy reporting
- Enhanced fairness metrics and memory pressure monitoring

Documentation:
- Add migration guide for v3.36.0
- Add operations/capacity-planning.md for enterprise deployments
- Update all examples and troubleshooting guides
- Rename monitor-lazy-mode.ts → monitor-cache-performance.ts
This commit is contained in:
David Snelling 2025-10-10 14:09:30 -07:00
parent 6037db3d85
commit 46c6af3f21
17 changed files with 2737 additions and 127 deletions

View file

@ -51,9 +51,13 @@ export type RebuildProgressCallback = (loaded: number, total: number) => void
*/
export interface RebuildOptions {
/**
* Lazy mode: Load structure only, data on-demand
* Saves memory at cost of first-access latency
* (HNSW: vectors loaded on-demand, Graph: relationships cached, Metadata: lazy field indexing)
* @deprecated Lazy mode is now auto-detected based on available memory.
* System automatically chooses between:
* - Preloading: Small datasets that fit comfortably in cache (< 80% threshold)
* - On-demand: Large datasets loaded adaptively via UnifiedCache
*
* This option is kept for backwards compatibility but is ignored.
* The system always uses adaptive caching (v3.36.0+).
*/
lazy?: boolean
@ -96,11 +100,16 @@ export interface IIndex {
* - Load data from storage using pagination
* - Restore index structure efficiently (O(N) preferred over O(N log N))
* - Handle millions of entities via batching
* - Support lazy loading for memory-constrained environments
* - Auto-detect caching strategy based on dataset size vs available memory
* - Provide progress reporting for large datasets
* - Recover gracefully from partial failures
*
* @param options Rebuild options (lazy mode, batch size, progress callback, force)
* Adaptive Caching (v3.36.0+):
* System automatically chooses optimal strategy:
* - Small datasets: Preload all data at init for zero-latency access
* - Large datasets: Load on-demand via UnifiedCache for memory efficiency
*
* @param options Rebuild options (batch size, progress callback, force)
* @returns Promise that resolves when rebuild is complete
* @throws Error if rebuild fails critically (should log warnings for partial failures)
*/