1 Reply Latest reply on Feb 12, 2015 4:31 AM by Fred(CH)

    Speed issues with FM 13

    RachelStanley

      Summary

      Speed issues with FM 13

      Product

      FileMaker Pro

      Version

      13

      Operating system version

      Windows 2008 - server, windows 7 users

      Description of the issue

      We have built a system for our clients that manages all processes within their company, quotes, schemes, billing time, clients, invoicing, reporting. Approx 70 users, windows 2008 server, citrix environment, 4 offices in the UK. They have serious speed issues.  The speed issues are not consistent, it is running on a highly specified server, if they previous system which was build in FM12 is run when they are experiencing a slow down this system will not slow down at the same time.  Their IT support have done numerous tests to rule out the network.  The places the system slows down is variable, when it is running fine we can navigate the system without any slow downs, where there is the slowdown and we navigate in the same way we can experience issues in different parts of the file.  This is why we believed it was a network issue first.  Our developer has changes some of the sql calculations to the former way of doing this and this has helped the speed slightly.

      Steps to reproduce the problem

      Log on at different parts of the day and run the same navigation through the system.

      Expected result

      Eliminate these speed issues.

      Actual result

      Speed issues are random and affect different parts of the file randomly.

      Exact text of any error message(s) that appear

      No errors, just the beach ball.

        • 1. Re: Speed issues with FM 13
          Fred(CH)

          Hi,

          If there are speed problem with the FileMaker database because all other possible causes were ruled out, there obviously are numerous possibilities; but very commons ones are related to unstored calcs.

          I just posted a product feedback here tuesday which provide one example of them : search on unstored calc. I had a script-specific problem and luckily, could solve it quite easily.

          But unstored calcs slowness, for instance in a list view, could be hard to solve because they are often structure-related.

          Our developer has changes some of the sql calculations to the former way of doing this and this has helped the speed slightly.

          Optimize formulas is obviously a good thing. But if a layout is displaying one or many unstored calcs and moreover, one or more of these conditions are met, it may not be enough :

                 
          1. Huge number of records being browsed on main table
          2.      
          3. One or more summary fields based on unstored calcs are displayed on the layout
          4.      
          5. Huge number of records are found on related table implied on the formula
          6.      
          7. The formula summarize one or more unstored calcs on related table
          8.      
          9. Etc...

           

          But maybe your developer already have checked all this and the problem is elsewhere...

          You also wrote "4 offices in the UK". Are the databases accessed within internet ? 

          Bye, Fred