Terrasync works fine for me, although it takes several minutes to download in dense scenery areas (Hartsfield Int). Once loaded it works great. If I turn off automatic scenery downloading and load from the retained Terrasync file, it loads quickly, but I get little loading skips when flying, which I don't get if when it's live on line. Think these skips are from loading from the hard drive; and would probably not exist if I was using a solid state drive. Like the way Terrasync adds and updates scenery where I'm flying. No complaints.
Flew A6 from Hartsfield this morning using 2017.2.1 on my Intel I3. Scenery installed almost instantly with automatic scenery downloading off and showed no sign of skips, which seems to be an improvement over 2017.1.3. Was using 14% processor, 1.4 MEG Ram, and .1% HD. Microsoft was simultaneously using about 25% in background for Windows Module Installer.
Reran with automatic scenery downloading on. Took exactly 3 minutes to download and install scenery. CPU use varied from 14 to 28%, which variation I suspect had mostly to do with internet and/or server.
Ran the A6 at Hartsfield using my AMD 8-7410 laptop. It took 7 minutes to download and install using TerraSync. Then noticed
Chrome was the default browser on the I3; whereas, Edge was the default browser on the AMD 8. Changed the default browser on the AMD 8 to Chrome. This time it took 4 minutes to download and install-not quite as good as on the I3, but a large improvement over using Edge.
Took 6 minutes on AMD 8-7410 using Firefox
Retried I3 using Explorer. Took 5 minutes versus 3 with Chrome, so sticking with Chrome for the time being...