Find All in Current Site makes UI non-responsive - CC 2017.0.1

Hi,

since the new major version CC 2017, whenever I search through "Current site..." the UI will hang until the search is finished, and I can't continue to work/look through files while searching. My coworker experience the same, however they solve the problem by not using search as much. This is new behavior, and happens to me oh so many times a day, since I... apparently search a lot.

Our site folders are large, say up to over 10k files over hundreds or thousands of directories. And this machine does not have a SSD, unlike the one at home. If I search for the same a second time, the result seems to be instant so there's some caching going on. However, most of the time the search aren't cached and the Dreamweaver UI comes to a temporary halt.

When I first tried search on my home computer, I was excited to see that search seemed much faster in some cases. However, when I started using it - which would be at work, not at home - I realized that there was this major drawback to the search, for the way I use it. I will often predict something I will need to look at next, and at that time I would start a search for that while still working/looking through the open files. That used to work fine, just the search was a bit slow, and that's why I started the practice of searching early. Now, this will trigger the busy icon, after 5-10 seconds the Dreamweaver window bar will turn white, say  "Adobe Dreamweaver CC 2017 - [filename] (Not responding)". It will stay like that for a while while searching, and if I try to do something it may trigger the painful and forgetful crash that one expect when clicking on a non-responding Dreamweaver.

I appreciate that switching the Dreamweaver code editor to the new Brackets-based editor is a major task, and that there will be teething problems. On the other hand, I also have learned that Adobe aren't one to come with many feature upgrades or bug fixes per major version. However, we've been informed that there are upcoming Find & Replace panel/ribbon/thingie fixes.

My questions are, did Dreamweaver change the way search process is threaded, since it now hangs the UI? And if so, is this something that will be changed with the upcoming fixes? Or is this just a problem due to too large site folders and/or our local configurations so that I have to break up the site in artificial logical subsites and/or throw in a SSD drive to get the UI to be unresponsive for shorter periods at the time? If this is because search just use more resources faster, then of course my solution would be to throw hardware at the problem.

Any insight?