4GB RAM is under the recommended minimum of 8GB. If possible add more RAM. You can try optimising the Java VM settings under Options/Performance and see if it helps, but at 4GB there’s little room for improvements.
You can find the performance settings in the menu. Under Tools / Options and then select the Performance tab.
I made a little comparison of opening a GeoTiff file. it Is only a small one (3000x1300 pixels), downloadable here. But you can see that reading has improved a lot between SNAP 6 and SNAP 7. Comparing SNAP 7 and the current dev version, there is no big improvement anymore. The videos below are ordered from top to bottom. SNAP_dev first, SNAP_7 and as last one SNAP 6.
However, the performance also depends on the specific file. With another file, you can get different results.
It could also be that the writing causes the problem. By the way, in the issue it is not said which data format is used for the output. But I guess GeoTiff.
This could already be the difference.
Original S1 data is compressed and the output not. More data needs to be read which takes more time. But I’m just guessing. I think Luis is investigating this.
No, only the viewing as you mentioned, but according to
I only guess, but, the file data is GLCM sigma0, VH, VV, is big, it is proceeding now as you see, but long-time, But I found under windows os, if the system sleeps, the processing using gpt sleeps as well, I resit the setting to be never sleep, it takes long time but it works fine.