Importing library takes ages for no apparent reason #4784
Unanswered
titivermeesch
asked this question in
Q&A
Replies: 1 comment 3 replies
-
You should use a single volume for storage and originals in this case (eg mount /photoprism), so that files can be moved/renamed when importing them. This will be much much faster. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
I'm currently trying to setup photoprism (docker-compose with mariadb) as my main photo/video storage but it seems impossible to import my library smoothly.
I started by upload some photos and videos (around 50GB) in the import folder (which I configured through the docker compose volumes).
A few pictures went through but now it seems to be stuck at videos. Here are the logs I got from the container:
As you see between 11:14 and 11:42 there are no logs, even though the videos were in the import folder. So it took around 30 minutes to start processing the next video, I'm not entirely sure what is going on.
The photoprism instance run on a Raspberry PI 4 B with 8GB of RAM along with 16GB swap and has a total of 4 cores (which don't seem to be used that much, the ram is also not above 1.5GB/8GB at any time).
Photoprism itself is running on a 500Gb SDD and the storage volumes are on a 5TB modern HDD.
I understand that since I'm running my storage on a HDD that reading or copying a 16Gb file may be a bit slow, but I would like to understand while it took 30 minutes between the 2 video files while that video file 0001 was 18Mb. 0002 on the other hand is a bit short of 18Gb
Anyone knows what the issue could be? Or is it just expected to have these kind of delays with video files?
Beta Was this translation helpful? Give feedback.
All reactions