Dikkiedick
IImmich
•Created by Dikkiedick on 4/28/2025 in #help-desk-support
Browser based timeline stuck on initial load every time - Redis errors?
Each time while using browser and click on the photos timeline I have like a minute of page not responding. Once it loads, it works, but not as fast as I am used to on my RPI4 (now using N100). App seems blazing fast. I have resetted my browser, used different browsers, platforms etc, no luck.
Using default docker-compose.yaml on portainer and only use a 40k external library.
I did notice the following in my redis server log (running Valkey), could this be related?
:M 28 Apr 2025 19:50:04.828 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 28 Apr 2025 19:50:04.828 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
1:M 28 Apr 2025 19:50:04.828 * Valkey version=8.1.0, bits=64, commit=00000000, modified=0, pid=1, just started
1:M 28 Apr 2025 19:50:04.828 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf
1:M 28 Apr 2025 19:50:04.828 * monotonic clock: POSIX clock_gettime
18 replies