Also, I was thinking if jAlbum could generate plain HTML pages for the individual images and redirect them to the real, dynamic page. However this is against Google's recommendations, and might be banned. This is what they call "design for robots".
As a human I prefer design for humans. I am pleased with Tiger search now working on mistelberger.net/Bilder (45701 Images, 3 Audio, 1198 Videos) with very reasonable performance.
Does Tiger search now work when building changed folders only?
Probably the search can skip inconsistencies within the folder tree - as far as I remember I've added error recovery -, but it can happen other functions not.
Tried building changed folders only of project /home/Albums/Bilder with 49,616 objects (total size 113 GB). The local album has 104,239 files in 4,550 folders (16 GB).
jAlbum 15.2 system console running BeanShell (BeanShell Engine)
Make album: 4.764s
Make album: 3.921s
Make album: 4.324s
Make album: 3.94s
Make album: 4.703s
Make album: 3.673s
Make album: 3.695s
The build overhead of checking all objects is a few seconds only.
Viewing the local album served by Apache running on the local host is very fast. Firefox Quantum instantaneously opens pages with some 100 folders and images.
Tiger Search is really fast: Loading 1,515 data1.json files (50 MB) and searching for a string takes a second. Subsequent searches with those files cached by the browser are instantaneous.
Tiger Search indeed finds all occurrences.
Building changed folders only fails to build index.html files pertaining to unchanged subfolders of the changed ones. This is readily fixed by touching the subfolders manually.
Moving albums to another machine (51.239 objects) is fast and reliable with jAlbum 15.3:
Make album: 5.879s
Album upload: 32.692s
Total upload: 42.199s 👍