Jump to a date: nothing displayed

[darrepac]

Hi

The app works ok.
I can see my pictures and can scroll down and it updates relatively quickly.
I have 30k pictures. So one major features I want is the timeline view with the possibility to jump into a particular period: it is implemented, good!
But when I use it, for example, I jump back to 08/2008, no photos are displayed. I just have grey squares.
At first I thought it was because the database was indexing and my raspberry pi overloaded.
But now that my files are indexed and the pi running without load, it doesn't work as expecting.

I have also the following issue (only the first 50 pictures are displayed: #103), so it may be linked?

[thejaykid7]

I believe the indexing takes awhile currently. I can produce the same issue on the iOS version of the app. There's some other issues like photo's are out of order in terms of the date, for example.

[darrepac]

I don’t think: I can let the app during lot of time, nothing is never displayed.
On the server and network sides, nothing showing that somrthing is going on.
As stated in my first post, I think that it is probably linked to the first 50 pictures only issue...

[gomme600]

For me it does show up but can be a bit slow. The further I jump the longer it seems to take. I wonder if it has to request 50 photos at a time? Also, I can't see very old photos. There seems to be some soft of limit. I have a photo from 2013 and it isn't showed in the app if I go to the very bottom of the list. Running a raspberry pi 4 8GB.

[darrepac]

For me it does show up but can be a bit slow. Running a raspberry pi 4 8GB.

you are right!! but it is very slow...which is strange
Took me 1min10 to get the pictures...on pi side, mysqld was taking 90% of the cpu during that time. Some says mysql need to be tweaked to run efficiently... but how?

[ohthehugemanatee]

I suspect the problem is that it is running refresh/index operations the whole way during the scroll. So god forbid you slow down somewhere, because it will load a ton of previews unnecessarily. The obvious way to work around this would be to insert a 250ms delay or something before triggering the remote server call, to reduce the false positive rate.

IF that's the problem, of course. :)

[ippocratis]

docker pull thielepaul/photoprism:db-api
Then rebuild with
image: thielepaul/photoprism:db-api
In
docker-compose.yml
Using.the db:api image can let you use the app with the latest backend changes and has not got the loading old images issues the official image has with this app
Also uncomment the watchtower lines to aouto audate the image as when an update is pushed and you are on an older image app cant display anytjing