3
[Feature] Separate thumbs storage location by quality
Source: immich-app/immich#17366 · opened by @mmomjian
I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.
• Yes
The feature
We now have 3 qualities of thumbs:
• thumbnail
• preview
• fullsize
Users may want to use flash storage for some but not all of these files. For example, on my system, the thumbnail WEBPs take 3 GB, while the preview JPEGs take 60 GB. Moving the thumbnails to an SSD would greatly improve the timeline experience.
Proposed solution: migrate thumbs to 3 subfolders:
• thumbs/thumbnail/<user UUIDs>
• thumbs/preview/<user UUIDs>
• thumbs/fullsize/<user UUIDs>
In this way users can mount varying storage to the subfolders and mix flash and HDD storage. This shouldn't be a breaking change, and we can use the Storage Migration job.
Platform
• Server
• Web
• Mobile
• Yes
The feature
We now have 3 qualities of thumbs:
• thumbnail
• preview
• fullsize
Users may want to use flash storage for some but not all of these files. For example, on my system, the thumbnail WEBPs take 3 GB, while the preview JPEGs take 60 GB. Moving the thumbnails to an SSD would greatly improve the timeline experience.
Proposed solution: migrate thumbs to 3 subfolders:
• thumbs/thumbnail/<user UUIDs>
• thumbs/preview/<user UUIDs>
• thumbs/fullsize/<user UUIDs>
In this way users can mount varying storage to the subfolders and mix flash and HDD storage. This shouldn't be a breaking change, and we can use the Storage Migration job.
Platform
• Server
• Web
• Mobile
No pledges yet. Be the first to back this.
Comments
Similar requests
[Feature] Separate Image Preview for Machine Learning
1 vote · 0 comments
[Feature] Multiple Storage Tiers with Automated Archiving
15 votes · 0 comments
Improvement Suggestions for Thumbnail Handling and Timestamp Preservation in Immich After Restore
3 votes · 0 comments
[Feature] Transcode policy for images (e.g. high res for heic only)
4 votes · 0 comments
[Feature] Path per user
63 votes · 0 comments
No comments yet.