memory usage as cache?
Hi
I noticed that there was still a lot of available ram (1.5 of 4 GB) on my win7 64bit system while using the latest 64-bit version of capture one. At the same time it was visible not caching info at 100% (imageview) , while I moved from right to left in the image and back the screen was recalculated (with a intermediate screen from the preview I suppose).
The same happened when I looked at an image for a couple of seconds and then zoomed in to 100%. I expected that the 100% view was already calculated in the background (while the CPU was idling), but this isn't the case.
I find this strange because throwing away something while there's memory available is strange and calculating something while the user isn't waiting makes the app having a lot faster appearance.
Alain
I noticed that there was still a lot of available ram (1.5 of 4 GB) on my win7 64bit system while using the latest 64-bit version of capture one. At the same time it was visible not caching info at 100% (imageview) , while I moved from right to left in the image and back the screen was recalculated (with a intermediate screen from the preview I suppose).
The same happened when I looked at an image for a couple of seconds and then zoomed in to 100%. I expected that the 100% view was already calculated in the background (while the CPU was idling), but this isn't the case.
I find this strange because throwing away something while there's memory available is strange and calculating something while the user isn't waiting makes the app having a lot faster appearance.
Alain
0
-
Hi
Just to add that it doesn't help to have more memory available, I switched to 8GB and it made no difference.
I also noticed that my CPU was only used 50% when using the loupe and moving around. Unfortunately there was room for improvement, the loupe was not updating fast.0
Post ist für Kommentare geschlossen.
Kommentare
1 Kommentar