Posts:
759
Registered:
13-Apr-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 19:50
in response to: RobM
|
|
|
The source (pictures/videos are all on a HDD) and the size of all of this is about 1,5 TB.
My guess at what’s slowing it down is JSON data processing. It must be like printing out War and Peace on every album build 
This can absolutely not be ruled out. As Jeff sometimes says somewhat mockingly, I'm the only one in the whole universe who uses such long comments in the albums.  But in a recent post I found out that there is another user with long comments. Couldn't remember who it was.
|
|
|
Posts:
8,090
Registered:
31-Jan-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:14
in response to: RobM
|
|
|
My guess at what’s slowing it down is JSON data processing.
That was my hunch, too. There's almost no other possible explanation. Generating the lifeboat file could be equally time-consuming, but it doesn't appear that MarkusD has that enabled.
|
|
|
Posts:
8,090
Registered:
31-Jan-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:17
in response to: MarkusD
|
|
|
Maybe you can spot anything of value. As you can see it took four minutes until the first object was processed. Does that ring a bell on your side?
Yes, it does. I think that's the core checking to see if any folder thumbnails need to be regenerated, and if you've got hundreds of folders, that could be a little slow. I'm not sure if there's any way to speed up that process.
|
|
|
Posts:
3,939
Registered:
4-Aug-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:25
in response to: MarkusD
|
|
|
What I can see at the start of make album is the yellow warning triangle appears almost straight away. java.io.IOException no image readers found for hurtgruten_logo_small.webp
...
Webp lossless format is not yet supported
|
|
|
Posts:
759
Registered:
13-Apr-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:26
in response to: JeffTucker
|
|
|
My guess at what’s slowing it down is JSON data processing.
That was my hunch, too. There's almost no other possible explanation. Generating the lifeboat file could be equally time-consuming, but it doesn't appear that MarkusD has that enabled.
Your are right. I enabled that option, compile and upload again. Will post if the upload is finished.
|
|
|
Posts:
759
Registered:
13-Apr-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:28
in response to: RobM
|
|
|
What I can see at the start of make album is the yellow warning triangle appears almost straight away. java.io.IOException no image readers found for hurtgruten_logo_small.webp
...
Webp lossless format is not yet supported
I have some of these error messages, but, this should not slow down the process.
|
|
|
Posts:
3,939
Registered:
4-Aug-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:29
in response to: RobM
|
|
|
|
And four minutes to compile Tiger's util.js and init.js
|
|
|
Posts:
759
Registered:
13-Apr-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:31
in response to: JeffTucker
|
|
|
Maybe you can spot anything of value. As you can see it took four minutes until the first object was processed. Does that ring a bell on your side?
Yes, it does. I think that's the core checking to see if any folder thumbnails need to be regenerated, and if you've got hundreds of folders, that could be a little slow. I'm not sure if there's any way to speed up that process.
Could it be a problem that I not only have some sub folders but also some sub folders which are *excluded*? Is it guaranteed that excluded objects (pictures, video but also sub-sub-sub-folders) are not processed in any way?
|
|
|
Posts:
3,699
Registered:
18-Oct-2002
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:31
in response to: JeffTucker
|
|
|
|
Marcus, it doesn't seem that you have checked "Include lifeboat file" under Preferences->Album, so I can't inspect your project settings. Please tick "include lifeboat file", then make and upload the gallery again.
I have a hunch on what could cause this extremely long initial delay though, and that is if you've set image ordering to "Camera ordering" everywhere. This will cause jAlbum to open each source image first. You can avoid this problem by cacheing the camera dates, and this can be done by switching to "Custom ordering" everywhere. jAlbum has an external tool called "Cache image ordering" that does just this. The only downside with this option is that you need to refresh the image ordering for folders where you add new images.
If this doesn't help, then open jAlbum's system console before your start an album build, then, as jAlbum has this very long initial delay, click the "Dump threads" button 2-3 times, ideally with 10 seconds delay, then pass me the generated files for inspection. They will tell me what jAlbum is up to.
|
|
|
Posts:
3,939
Registered:
4-Aug-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:32
in response to: MarkusD
|
|
|
What I can see at the start of make album is the yellow warning triangle appears almost straight away. java.io.IOException no image readers found for hurtgruten_logo_small.webp
...
Webp lossless format is not yet supported
I have some of these error messages, but, this should not slow down the process.
It takes two minutes to get past that image, but more importantly is the yellow warning triangle means a problem exists that should be fixed. I'm not sure if such errors can have knock-on effects. So I would not be using lossless webp images at all.
|
|
|
Posts:
759
Registered:
13-Apr-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:49
in response to: davidekholm
|
|
|
Marcus, it doesn't seem that you have checked "Include lifeboat file" under Preferences->Album, so I can't inspect your project settings. Please tick "include lifeboat file", then make and upload the gallery again.
I just finished another upload of my album. Lifeboat file:
https://www.markus-drueck.de/norge/lifeboat.zip
I have a hunch on what could cause this extremely long initial delay though, and that is if you've set image ordering to "Camera ordering" everywhere. This will cause jAlbum to open each source image first. You can avoid this problem by cacheing the camera dates, and this can be done by switching to "Custom ordering" everywhere. jAlbum has an external tool called "Cache image ordering" that does just this. The only downside with this option is that you need to refresh the image ordering for folders where you add new images.
OK, I read about that some weeks (or month) ago but I was not sure if this would effect the compile times of my album.
I honestly am a bit afraid of using the tool "Cache image ordering" and end up in a big chaos of the sort order of my album. Yes, of course, I do have several backups of my whole system but restoring them is not I want to do.
I'll see if I can test this on my notebook. I do have a 1:1 copy (except the videos) from my PC on the notebook. So simulating what happens when I use the tool "Cache image ordering" is possible without changing my original system. I'll try that at the weekend and let you know.
Thanks so far.
|
|
|
Posts:
759
Registered:
13-Apr-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 20:55
in response to: RobM
|
|
|
What I can see at the start of make album is the yellow warning triangle appears almost straight away. java.io.IOException no image readers found for hurtgruten_logo_small.webp
...
Webp lossless format is not yet supported
I have some of these error messages, but, this should not slow down the process.
It takes two minutes to get past that image, but more importantly is the yellow warning triangle means a problem exists that should be fixed. I'm not sure if such errors can have knock-on effects. So I would not be using lossless webp images at all.
I created that file myself:
https://www.markus-drueck.de/JA/hurtigruten_logo_small.webp
Is there anything wrong with it? I displays well. I use it in the second table ("Statistiken") - in the header row - on this page:
https://www.markus-drueck.de/norge/Misc/Mobility/index.html
|
|
|
Posts:
3,939
Registered:
4-Aug-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 21:13
in response to: MarkusD
|
|
|
What I can see at the start of make album is the yellow warning triangle appears almost straight away. java.io.IOException no image readers found for hurtgruten_logo_small.webp
...
Webp lossless format is not yet supported
I have some of these error messages, but, this should not slow down the process.
It takes two minutes to get past that image, but more importantly is the yellow warning triangle means a problem exists that should be fixed. I'm not sure if such errors can have knock-on effects. So I would not be using lossless webp images at all.
I created that file myself:
https://www.markus-drueck.de/JA/hurtigruten_logo_small.webp
Is there anything wrong with it? I displays well. I use it in the second table ("Statistiken") - in the header row - on this page:
https://www.markus-drueck.de/norge/Misc/Mobility/index.html
It looks fine with exiftool, but why not make the image as a plain webp instead of a lossless one?
|
|
|
Posts:
8,090
Registered:
31-Jan-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 21:44
in response to: RobM
|
|
|
|
|
It looks fine with exiftool, but why not make the image as a plain webp instead of a lossless one?
It's definitely a format that jAlbum can't handle. If added to a project, it can't show a thumbnail, and it won't process the image. No problem if I simply convert it to a PNG. It's OK as a JPG, too, of course.
|
|
|
Posts:
759
Registered:
13-Apr-2006
|
|
|
|
Re: Time stamp in the console
Posted:
5 Oct 22, 21:55
in response to: JeffTucker
|
|
|
It looks fine with exiftool, but why not make the image as a plain webp instead of a lossless one?
It's definitely a format that jAlbum can't handle.
Jeff, I use that file in the res folder only. It is not part of the album, as a regular picture. But it seems now to me that jAlbum nevertheless does "something" with that file and complains about it.
OK, I'll replace my "hurtigruten_logo_small.webp" with your png file. Thanks.
The bad thing about the triangle in the lower status line is, I never look at it, it is kind of invisible to my eyes. In our own applications, if there is an error, the user will get a message box, which he has to confirmed. So it is impossible to miss a critical situation. Yes, I know, that is not very nice but how should I cure a problem I never noticed. This is just my thought about the triangle in the status line.
|
|
|
|
Legend
|
|
Forum admins
|
|
Helpful Answer
|
|
Correct Answer
|
|