Cache slows down viewing

[kem]

Hi, I am using XnView for many years. I need very fast and smooth vieving for I frequently work with digital video frames.

I have been pretty disapointed with last version of XnView. Looping in view mode (holding PgDown key down) is 10x slover than in previous version. I did some trials in options settings and found out the problem is in caching. When I unchecked both "Read one image ahead" and "Keep current image in cache" then it is much more (10x) faster. It seems there is bug in caching.

[xnview]

Hi, I am using XnView for many years. I need very fast and smooth vieving for I frequently work with digital video frames.

I have been pretty disapointed with last version of XnView. Looping in view mode (holding PgDown key down) is 10x slover than in previous version. I did some trials in options settings and found out the problem is in caching. When I unchecked both "Read one image ahead" and "Keep current image in cache" then it is much more (10x) faster. It seems there is bug in caching.

Which version do you use, this problem is fixed in 1.80.3

[Sleepy]

Hi, I am using XnView for many years. I need very fast and smooth vieving for I frequently work with digital video frames.

I have been pretty disapointed with last version of XnView. Looping in view mode (holding PgDown key down) is 10x slover than in previous version. I did some trials in options settings and found out the problem is in caching. When I unchecked both "Read one image ahead" and "Keep current image in cache" then it is much more (10x) faster. It seems there is bug in caching.

Which version do you use, this problem is fixed in 1.80.3

Hello,
I am using 1.80.3 Minimal version right now.
However, I still have the problem that it takes some time to view the next image even though I check "Read One Image Ahead". I could see the bar reading the image in the right-bottom corner after I switch to next image. It seems that the image is not read in advance.
Could anyone please tell me how I could solve this problem???

Thank you very much.

[xnview]

Hi, I am using XnView for many years. I need very fast and smooth vieving for I frequently work with digital video frames.

I have been pretty disapointed with last version of XnView. Looping in view mode (holding PgDown key down) is 10x slover than in previous version. I did some trials in options settings and found out the problem is in caching. When I unchecked both "Read one image ahead" and "Keep current image in cache" then it is much more (10x) faster. It seems there is bug in caching.

Which version do you use, this problem is fixed in 1.80.3

Hello,
I am using 1.80.3 Minimal version right now.
However, I still have the problem that it takes some time to view the next image even though I check "Read One Image Ahead". I could see the bar reading the image in the right-bottom corner after I switch to next image. It seems that the image is not read in advance.
Could anyone please tell me how I could solve this problem???

Always the problem in 1.80.3??, you view your picture in fullscreen? After pressing F11 for example?

[Guest]

Always the problem in 1.80.3??, you view your picture in fullscreen? After pressing F11 for example?

It happens no matter in Fullscreen or in View Screen.
But in the "View Screen", I could tell from the "progress bar" and "Press ESC to abort" in the statu bar.

[xnview]

Always the problem in 1.80.3??, you view your picture in fullscreen? After pressing F11 for example?

It happens no matter in Fullscreen or in View Screen.
But in the "View Screen", I could tell from the "progress bar" and "Press ESC to abort" in the statu bar.

Could you tell me if you have the problem from browser by pressing F11?

[Sleepy]

Always the problem in 1.80.3??, you view your picture in fullscreen? After pressing F11 for example?

It happens no matter in Fullscreen or in View Screen.
But in the "View Screen", I could tell from the "progress bar" and "Press ESC to abort" in the statu bar.

Could you tell me if you have the problem from browser by pressing F11?

I could jump to Fullscreen by pressing F11 from browser with any problem.
However, even I view the pics in FullScreen, the issue (not reading one image ahead) still exists.

[xnview]

I could jump to Fullscreen by pressing F11 from browser with any problem.
However, even I view the pics in FullScreen, the issue (not reading one image ahead) still exists.

Someone with the same problem (1.80.3)????

[klaus2]

Concerning the issue "Looping in view mode (holding PgDown key down)" i already reported earlier that with 1.80.3 and "read one image ahead" for me it seems to slow down visibly (full screen or not does not play a role).

... at least it appears so when you browse through a image list using frequently PgDown (in the viewer).

When i say "appears" i mean that this may be a subjective impression, due to the fact that while you're seeing image "n", in the background images "n+1", "n+2", "n+3" ... are processed (seen via caption and statusbar msg) without being displayed at that time.
That leads to the impression of a certain delay (with other words: time is spent for to calculate the next 10,20 .. pictures but no
compute time is left for to show the neighbouring next picture).

My personal fix is to set "read one image ahead" to "off" anyhow.
There's another thread here (cancel paint operation if meanwhile next image is requested), that could speedup stepping forward drastically.

klaus2
Additonal remark: as there's oftenly the comparison with acdsee, acdsee (at the same situation: keep PgDown pressed) lets the viewer area black until an image is fully read, so when stepping forward fast at least you have the impression it's speedier (whereas you cannot see any picture at that time ..).
For me xnview's approach is better (but without 'read one image ahead = on').

[Sleepy]

I could jump to Fullscreen by pressing F11 from browser with any problem.
However, even I view the pics in FullScreen, the issue (not reading one image ahead) still exists.

Someone with the same problem (1.80.3)????

Am I still the only one who has this issue???

[Sleepy]

I could jump to Fullscreen by pressing F11 from browser with any problem.
However, even I view the pics in FullScreen, the issue (not reading one image ahead) still exists.

Someone with the same problem (1.80.3)????

Am I still the only one who has this issue???

I don't know the reason but the reason was solved after I changed the language. Even though I changed it back to English, Xnview works properly.
Although it's kind of weird, anyways, it's solved right now.

Thanks for everyone's reply.

[cozdas]

I'm seing the same problem too...

I used filemon from sysinternals to se what's going on, I see that XnView reads all of the files in the directory after hitting pagedown.

here is the log file.

Hope this helps

[xnview]

I'm seing the same problem too...

I used filemon from sysinternals to se what's going on, I see that XnView reads all of the files in the directory after hitting pagedown.

here is the log file.

Hope this helps

So to understand this problem, you open a file by the browser (enter or dbl click), you are in the view mode, and you press PgDown. Right?

[cozdas]

correct,

But please note that the log I sent you only shows the portion after I pressed the pagedown. also I've noticed that the pictures in the log are the ones that are ahead of the current file (it didn't read the pictures whose names are smaller than the current one)

In more detail:
the pictures in that folder are DSCN7305 to DSCN8063 (total of 263 files with some missing file names)

I double clicked DSCN7339 and pressed pagedown to advance to DSCN7340. Then XnView read all the files from that point to the end (i.e. read all pictures between DSCN7340 and DSCN8063) in 2.5 seconds.

This happens only when the "read one image ahead" option is on. Looks like that option behaves like "read all images ahead"

[xnview]

correct,

But please note that the log I sent you only shows the portion after I pressed the pagedown. also I've noticed that the pictures in the log are the ones that are ahead of the current file (it didn't read the pictures whose names are smaller than the current one)

In more detail:
the pictures in that folder are DSCN7305 to DSCN8063 (total of 263 files with some missing file names)

I double clicked DSCN7339 and pressed pagedown to advance to DSCN7340. Then XnView read all the files from that point to the end (i.e. read all pictures between DSCN7340 and DSCN8063) in 2.5 seconds.

This happens only when the "read one image ahead" option is on. Looks like that option behaves like "read all images ahead"

Only when you have this setting, very strange. Could you tell me which sort setting do you have in the browser?