mirror of
https://github.com/photoprism/photoprism-docs.git
synced 2026-04-25 02:35:50 +03:00
[GH-ISSUE #21] Data fragmentation and database #9
Labels
No labels
bug
docs 📚
done
enhancement
enhancement
help wanted
idea
low-priority
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism-docs#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KITblue on GitHub (Sep 19, 2020).
Original GitHub issue: https://github.com/photoprism/photoprism-docs/issues/21
Originally assigned to: @lastzero on GitHub.
The number of images generated by the program is too large, fragmentation is serious, and it has a great impact on the hard disk. Do you want to consider using a database
@lastzero commented on GitHub (Sep 19, 2020):
Haven't heard the word fragmentation for a very long time. What file system?
You typically wouldn't store files in a database. And if you do, the database might as well store them as individual files or suffer from fragmentation if stored in a single binary.
@lastzero commented on GitHub (Sep 20, 2020):
This question on Stackexchange seems related:
https://unix.stackexchange.com/questions/28756/what-is-the-most-high-performance-linux-filesystem-for-storing-a-lot-of-small-fi
TL;DR: Performance and fragmentation depend a lot on the specific file system
Money quote:
@lastzero commented on GitHub (Sep 20, 2020):
I'll close this, since the repo is for our docs only.
If you have a specific feature request or bug report, you're welcome to open an issue in our main repo:
https://github.com/photoprism/photoprism/issues