Scratch that, problem persists.
I have also identified Chrome and Norton as possible problems with FileMaker. I had a Chrome window open with multiple tabs and left it open. FileMaker slowed down. I closed Chrome, FileMaker began running much better.
Norton and Microsoft will bomb FileMaker with their Stealth Updates.
Also, keep in mind the ancient recommendation: do not deploy a new version as soon as it ships but use it for testing on a backup copy and do not deploy on a network until you have thoroughly vetted it. Note that this advice from many experienced developers is missed or ignored by many who then resort to posting their problems.
I am trying the recommendations in the page you showed and will check back later.
After making those changes and restarting everything seemed OK. A couple hours later, the problem returned. A restart alleviated them once again. Perhaps some sort of memory leak is going on?
Can't address the memory leak question but it is obvious that once we start filling up memory and the virtual memory that this will cause a slowing of software actions just as it takes longer to search or sort a million records vs a hundred.
It is the nature of the first release of FIleMaker or any other software to be buggy and that within a few updates many of the bugs will be fixed.
Companies cannot afford to not release buggy software as the process of producing bug free software is both impossible and would be very time consuming affecting the release of new profitable versions.
I think what could be done instead is to address portions of a software application and issue incremental updates, this is already being done for bug fixes. The software could be sold with a buyin price and then a monthly subscription. Stop the subcription and no more updates and you have to buy in again at the new price. Thus popovers might get shipped in January and Menu Bars shipped in August, etc. rather than everything jammed into one big new version. New featues could be plugins, more or less.