viewer reads ENTIRE folder in background -> SLOW ! (1.91.
Posted: Sun Sep 09, 2007 2:27 pm
hi
sorry if this has been asked before,
but i searched for keywords:
slow, large folder, freezing, ...
without finding a solution here
furthermore, idont know if/claim that
the behaviour described beneath is a bug,
i just havent found a setting/param to fix it...
Use case:
-------------------
- igot a local folder with about 170 jpg images,
- yes, only 170 files, ONLY unharmed jpg files, each 1024x819, with no exif info
- double clicking a single image opens viewer of xnview immediately
- the selected image is displayed quite fast ....
Problem A:
-------------------
- ... buuuuuut: then, shortly after, my cpu gets 100% load -> xnview.exe munching most of the cpu time
- xnview is not responding (=completely blocked) for about 3 minutes (180s !!!)
- (note: the time of the lag/freezing/blocking depends on the size of the folder/number of images!)
- then, after ~3min, cpu load is back to normal, xnview is responding normally/quickly again
- even browsing (=xnview browser) through the current (=LARGE) folders is (now) rather "fast" and responsive
Problem B:
-------------------
- if "ReadAhead=0" is set instead of "ReadAhead=1" in xnview.ini problem does NOT occur ...
=> viewer opens immediately with xnview NOT eating up all my cpu time
- ... buuuuuuut: as soon as i hit "PageUp", "PageDown", "Pos1" or "End"...
- Voila, "Problem A" (see above) shows its ugly face again
Question:
-------------------
1) what is the so called 'viewer' doing on the background ???
it's called a "viewer", it should just read in a single or maybe 3 images (prev,current,next)
instead it OBVIOUSLY is reading in the COMPLETE content of the current folder !!!
2) is this is a bug, or something that can be disabled via parameters ?
System
-------------------
- my pc is rather outdated pIII, 1GHz, single core :)
- still harddisks are rather new/fast (2 x samsung 250GB sata)
- winxp pro sp2
- xnview 1.91.4
thx in advance
bottom
sorry if this has been asked before,
but i searched for keywords:
slow, large folder, freezing, ...
without finding a solution here
furthermore, idont know if/claim that
the behaviour described beneath is a bug,
i just havent found a setting/param to fix it...
Use case:
-------------------
- igot a local folder with about 170 jpg images,
- yes, only 170 files, ONLY unharmed jpg files, each 1024x819, with no exif info
- double clicking a single image opens viewer of xnview immediately
- the selected image is displayed quite fast ....
Problem A:
-------------------
- ... buuuuuut: then, shortly after, my cpu gets 100% load -> xnview.exe munching most of the cpu time
- xnview is not responding (=completely blocked) for about 3 minutes (180s !!!)
- (note: the time of the lag/freezing/blocking depends on the size of the folder/number of images!)
- then, after ~3min, cpu load is back to normal, xnview is responding normally/quickly again
- even browsing (=xnview browser) through the current (=LARGE) folders is (now) rather "fast" and responsive
Problem B:
-------------------
- if "ReadAhead=0" is set instead of "ReadAhead=1" in xnview.ini problem does NOT occur ...
=> viewer opens immediately with xnview NOT eating up all my cpu time
- ... buuuuuuut: as soon as i hit "PageUp", "PageDown", "Pos1" or "End"...
- Voila, "Problem A" (see above) shows its ugly face again
Question:
-------------------
1) what is the so called 'viewer' doing on the background ???
it's called a "viewer", it should just read in a single or maybe 3 images (prev,current,next)
instead it OBVIOUSLY is reading in the COMPLETE content of the current folder !!!
2) is this is a bug, or something that can be disabled via parameters ?
System
-------------------
- my pc is rather outdated pIII, 1GHz, single core :)
- still harddisks are rather new/fast (2 x samsung 250GB sata)
- winxp pro sp2
- xnview 1.91.4
thx in advance
bottom
