However, the processing bar was stuck at 46% for eight hours. Someone in the forum suggested that monster-graph is less memory-effecient than tiny-graph and may be the reason. So I splitted the graph and run the workflow before Interferogram node, as following:
Again, the processing bar is stucked. What puzzles me most is the fact that the CPU and GPU usage is extremly low, indicating my pc is not working hard. Why could this happen? Thanks in advance for any hints.
Dear ABraun. After reading posts related to this issue in the forum, I found that low usage of CPU and GPU is a known issue and @marpet mentioned in the post that some improvement would be made in next release. Right now, the workarounds I can image to speed up the processing are moving the files from mechanical hard disk to solid state disk, having better internet speed and configuering SNAP performance settings. I have tried all of these. Do you have any workarounds?
Dear @ABraun, I find the cause. It is the digital elevation model data that failed to automatically download in back-geocoding operation. Strangly, it kept silent without raising file-not-found error. Instead of use the built-in DEM in dropdown, I used external DEM which had been downloaded in local computer and then, task was done successfully. Hope my solution is helpful to someone.