I am often processing large datasets that may take 10s of hours to finish. It's a bit annoying that during that time the CPU is totally locked to Photoscan; even mouse movements are very sketchy. My idea was to commit only part of total CPU cores to Photoscan (say, 6 of 8 ) and leave the rest free for doing everyday tasks like running office programs and email client. I am not in a hurry so I don't mind if processing will take longer that way.
Following the instructions (e.g.
http://technet.microsoft.com/en-us/magazine/ee851672.aspx) I used Task Manager to assign the desired number of cores to photoscan.exe process.
To my surprise, computer remains totally unresponsive. Performance graphs in Task Manager (or in other CPU utilities) clearly show that two cores are not doing any work, but I see absolutely no difference in computer responsiveness compared to normal scenario when all cores were dedicated to Photoscan. For testing, I tried running a YouTube music video along Photoscan. YouTube used only ~22% of the free cores, however playback was interrupted all the time - it would play for 1-2 minutes, then it would go silent for 1 minute, then resume... and so on.
What is going on? Is it possible at all to set Photoscan to leave some of the processing power to other tasks?
My usual strategy is otherwise to pause Photoscan when I want to do some work, but this is quite annoying as due to computer unresponsiveness it takes me up to several minutes to position the mouse cursor on the Pause button and wait for Photoscan to react to the mouse click.
I am running Win 7 Pro on a machine with 32 GB RAM, of which only ~35% is used by Photoscan and all other processes.
Marko
Topic: Assigning processor core(s) to Photoscan has no effect? (Read 7458 times)
