5 Replies Latest reply on Nov 21, 2011 4:30 PM by philmodjunk

    Filemaker slow, bogged down

    MikeF

      Title

      Filemaker slow, bogged down

      Post

       

      I now have a lot of related tables, with a lot of calculated fields [but no summary fields], with new windows opening with portals, etc.

      ... But not a lot of records.  Max of 200 or so in the largest table.

       

      Understanding this is an extremely broad overview ...

      Opening the database now takes around ten seconds.

       

      For a new window to open it takes at least the same, and the refresh [ie records being loaded] can be watched almost record-by-record.

      Am concerned I've loaded the system down.   It's not the hardware [Core i7, 16gb's ram, etc].

       

      Again, this is an extremely broad overview, but does anyone have some direction in this regard?

      Thanks,

         Mike

       

       

        • 1. Re: Filemaker slow, bogged down
          philmodjunk

          with a lot of calculated fields

          Are these calcualtion fields that use aggregate functions such as Sum, Average, count, etc?

          Using very many filtered portals?

          Conditional formats?

          Layout based script triggers that fire when a new window or layout is opened?

          Every one of these features adds to the "load"--especially expressions that pull data from multiple related records.

          You may want to work from copies of your file, slectively deleting different features such as these from the copies to see what aspect of your design has the most impact.

          with new windows opening...

          How many windows are you opening? and Why?

          Especially on windows systems, I try to keep the number of windows to no more than two visible at any one time, one for the "main view" and one serving as needed as a modal dialog (has way more interface options than show custom dialog). I'm not totally sure on this but suspect that each window open in the background may require processor time updating the window even though it is not visible. You might try switching all such nonvisible windows to a layout that's blank and has a found set of zero records to see if it affects the behavior of your file.

          For 200 records on a non-networked file, this sounds extremely slow so you need to do some sleuthing to try to figure out why this is the case here.

          • 2. Re: Filemaker slow, bogged down
            MikeF

             

            Are these calcualtion fields that use aggregate functions such as Sum, Average, count, etc?

               Yes, lots of sums.  Summing detail fields from related tables into one record in summary tables.  Would "Summary" fields be better?

             

            Using very many filtered portals?

               No, none yet.

             

            Conditional formats?

               Just a few, nothing major.

             

            Layout based script triggers that fire when a new window or layout is opened?

              Very few.  Am using a few field-related Script Triggers ie Record Commit/Refresh Window.

             

            Also, using a downloaded Custom Function "TypeSumField" that works very well for "SUMIF" with expense categories. It's "sumif-ing" records from a related detail table into a summary table.

             

            with new windows opening...

            How many windows are you opening? and Why?

            First window is an executive summary of different projects in a portal. Clicking on a button beside a project in that portal opens .... 

            Second window, a more detailed summary of the project that was clicked on, which contains portals from related tables.  Clicking on a button in that portal opens ....

            Third window, a detail of the event in the second window's portal that was clicked.      [Was I clear enough on this???}

             

              Mike

             

             

             

            Every one of these features adds to the "load"--especially expressions that pull data from multiple related records.

            You may want to work from copies of your file, slectively deleting different features such as these from the copies to see what aspect of your design has the most impact.

             

            • 3. Re: Filemaker slow, bogged down
              philmodjunk

              Yes, lots of sums.  Summing detail fields from related tables into one record in summary tables.  Would "Summary" fields be better?

              Also, using a downloaded Custom Function "TypeSumField" that works very well for "SUMIF" with expense categories. It's "sumif-ing" records from a related detail table into a summary table.

              I'd definitely take a closer look at both of these. LaRetta has posted here that using Summary fields in place of Sum will require fewer system resources so it's worth a shot. Note that either option will not place any load on your system until you pull up a layout that displays them. This should not then affect how fast a window or the entire file opens unless the windows in question are opening to a layout that includes these calculation or summary fields.

              I'd also take a look at that "sumIf" function. It's likely a recursive function that computes and returns a value after making one or more loops through your data. That looping will definitely slow you down. You may want to consider alternatives that do not require the use of this custom function.

              Field based script triggers such as onObjectEnter will not be a factor here. Layout based ones such as OnLayoutEnter or OnRecordLoad can be a factor as they will run scripts automatically when you access the layout where they are set up and it's easy for one layout based trigger to trip other layout based triggers--reulting in a chain reaction of scripted calls or even an infinite loop.... Not what you seem to have here, but FYI...

              • 4. Re: Filemaker slow, bogged down
                MikeF

                 

                 Note that either option will not place any load on your system until you pull up a layout that displays them. This should not then affect how fast a window or the entire file opens unless the windows in question are opening to a layout that includes these calculation or summary fields.

                     Just checked, and the above is correct ... when loading a layout that doesn't include any of the tables with lots of summed fields.

                     Problem is those are the required layouts for the system.

                 

                   Mike

                • 5. Re: Filemaker slow, bogged down
                  philmodjunk

                  Yes, but you need only display one at a time so at the very least, you need not have this be a factor when the file is first opened.

                  Have you tried replacing the calculation fields with summary fields deifned in the table being summed?

                  There are several options for computing the sum of selected records in a related table that do not require using a custom function.