Skip to content
Phosor
Internal Beta

Performance

Beta Status

Phosor is currently in an Internal Beta stage. Performance continues to improve throughout the beta. Performance may occasionally be inconsistent depending on hardware, image formats, and library size. Unexpected bugs may still occur. Feedback from beta testers is highly appreciated.

This page covers Phosor's performance characteristics and what to expect during use.

Preview Loading

Standard Images (JPEG, PNG, WebP)

Previews appear quickly after loading. Smaller web-ready images open nearly instantly.

RAW Files

RAW files are displayed and sorted like any other supported image. Performance is comparable to standard image preview generation.

Frequently Viewed Images

Reopen instantly. Once a photo has been viewed, returning to it is immediate.

Adjacent Photos

Preloaded in the background after each navigation, so the next photo is often ready before you navigate to it.

  • Rapid key presses do not cause flickering or stale image display.
  • The viewer remains stable even during fast navigation.

Smooth navigation

You can navigate as fast as you can press keys without visual artifacts.

Memory Management

  • Background memory use is automatically limited to keep the application lightweight.
  • The application is designed to handle long sorting sessions without significant lag.

Large JPEG files

Very large JPEG files may cause memory spikes. See Known Issues for details.

Batch Move Performance

  • File moves are processed with real-time progress updates.
  • A single file failure never aborts the entire batch — the operation continues with remaining files.

Performance Notes

Ongoing Optimization

Performance continues to improve throughout the beta. We are actively working to optimize preview loading, navigation, and batch operations.

High-Resolution Images

Extremely high-resolution images or uncommon RAW formats may require additional processing time. If you work with 45 MP+ cameras or large RAW files, consider using the Highly Suitable hardware tier.

Storage and Memory

Large photo libraries benefit significantly from SSD storage and additional memory. For libraries containing thousands of photos, we recommend at least 16 GB of RAM and an NVMe SSD.

Known Performance Considerations

Large JPEG Files

Very large JPEG files may cause memory spikes. See Known Issues for details.

Cross-Device Moves

Moving files between different filesystems (e.g., from an external drive to the internal drive) may take longer. Verify file integrity after cross-device moves.

Concurrent Folder Changes

Rapidly changing the source folder while a scan is in progress may cause unexpected behavior. Wait for the scan to complete before switching folders.

See Also