OptimizedArtworkData class

An optimized version of ArtworkData with advanced memory management features.

OptimizedArtworkData extends the basic ArtworkData functionality with:

• Automatic caching with memory pressure handling
• Streaming support for very large images
• Compression for memory efficiency
• Smart loading strategies based on image size
• Performance monitoring and metrics

This class is designed for applications that need to handle large numbers of artwork images efficiently while minimizing memory usage.

Features

• Smart Loading: Automatically chooses between lazy, streaming, or cached loading
• Memory Optimization: Uses compression and caching to minimize memory footprint
• Size-Based Strategy: Different handling for small, medium, and large artwork
• Performance Tracking: Monitors loading times and cache effectiveness
• Backward Compatibility: Drop-in replacement for standard ArtworkData

Usage Examples

Basic Usage (Drop-in Replacement)

final optimizedArtwork = OptimizedArtworkData(
  mimeType: 'image/jpeg',
  type: ArtworkType.frontCover,
  description: 'Album cover',
  dataLoader: () => loadImageBytes(),
);

// Works exactly like ArtworkData
final imageBytes = await optimizedArtwork.data;

With Custom Cache

final cache = ArtworkCache(maxMemoryBytes: 100 * 1024 * 1024);

final artwork = OptimizedArtworkData(
  mimeType: 'image/png',
  type: ArtworkType.frontCover,
  dataLoader: () => loadImageBytes(),
  cache: cache,
  cacheKey: 'album_123_cover',
);

Streaming Large Images

final largeArtwork = OptimizedArtworkData(
  mimeType: 'image/jpeg',
  type: ArtworkType.frontCover,
  dataLoader: () => loadLargeImageBytes(),
  enableStreaming: true,
  streamingThreshold: 5 * 1024 * 1024, // 5MB
);

// Process in chunks for large images
if (largeArtwork.shouldUseStreaming) {
  await for (final chunk in largeArtwork.streamData()) {
    processImageChunk(chunk);
  }
}

Memory Management Strategy

The class uses a tiered approach based on image size:

1. Small images (< 100KB): Direct loading, no caching overhead
2. Medium images (100KB - 5MB): Lazy loading with optional caching
3. Large images (> 5MB): Streaming with minimal memory footprint

Performance Considerations

• Cache lookups add minimal overhead for cache hits
• Compression is only applied when beneficial (> 10% savings)
• Streaming adds processing overhead but eliminates memory spikes
• Size thresholds can be tuned based on application requirements