Downloaded tubearchivist two or three weeks ago and I don’t know if it’s just me but good lord any operations that involve the index (indexing new videos, rescanning or rebuilding the index, etc) are just abysmally slow. All of the app data is installed to an NVMe and the downloads go to my NetApp shelf which I’ve clocked hitting up to 1gb/s (byte not bit) writes and 2gb/s reads sustained (under ideal conditions, but still) so it’s not like the storage is slow, and I’ve even tried giving the container all 12 cores and 10 gigs of RAM to use but doesn’t help at all (not surprising because even with the default 2 cores it never even registers 1% CPU usage). Is this just normal for this app or is it somehow in my end? For example, the first few days I downloaded 150 videos and at that point decided to move out of the ixvolume and into a dataset so I reinstalled it configured as such and then did a rescan so it would find and index what I already had so it didn’t have to be redownloaded. It took 3 whole literal days for it to finish. That doesn’t seem right at all.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| [SOLUTION] Tube Archivist Elasticsearch Container Unhealthy - Fix: Add NFSv4 ACL Entry for UID 1000 | 3 | 239 | November 12, 2025 | |
| App Installation Takes long time | 1 | 79 | March 10, 2026 | |
| Very very slow docker extract after pull | 3 | 432 | October 27, 2025 | |
| Apps and VM disk occupation | 0 | 38 | June 3, 2025 | |
| Custom app, bad performance after dragonfish update | 0 | 176 | April 25, 2024 |