5 Replies Latest reply on Mar 20, 2015 8:38 AM by BryceKeller

    Filemaker 13 Charting Poor Performance Between Environments with Same Operating Systems Windows 8.1...

    BryceKeller

      Title

      Filemaker 13 Charting Poor Performance Between Environments with Same Operating Systems Windows 8.1 and Yoesemite 10.10

      Post

      We have an unusual situation and are in serious need of feedback/assistance from Filemaker.

      We have spent the past 3 months developing a system.  In our environment all elements of the system run and fire within a 1-2 second window.  We are in Spain but we use North American settings.  The client that the system was developed for is in the United Kingdom.

      It is a sales driven module that has customized user based side dash reporting on the dashboard and in all other major areas of the system.  Currently the figures are displayed via standard bar charting.

      When the client in the United Kingdom opens the file and attempts to access the dashboard it completely crashes on both platforms (Windows 8 and Yosemite).  To the best of our knowledge the client's machines meet all technical specifications for Filemaker 13.  In our environment we have even moved it to the smallest machine that we have which is a standard retail HP laptop with 6GB of installed RAM and it still runs in a 1-2 second window.  We have also sent it out to another Filemaker Developer in North America and their performance matches ours.

      We have never seen anything like this in 15 years of Filemaker Development.  Initially we thought that the sole cause of this might be caused by aggregates, summaries, etc.  So we went back to the drawing board and released or reconfigured the majority of the summaries in the system and made the charts SQL driven so that the link to the sales summary table could be separated.

      Once this was completed we saw an improvement in performance on our machines, but again in the client environment in the United Kingdom the system still completely crashes.

      Next we had the client remove the charting element from the layouts as a test.  Once the client removed the charting element from the layout, the system freed up and ran at the proper speed. 

      In an attempt to isolate the issue further we have produced 3 versions of the system.  The first version with the charting, the second version without the charting, the third one the plain SQL driven aggregate data.  It is the rendering or presence of the actual chart that for some reason is crashing their system completely.  Again on our systems it runs in 1-2 seconds without fail even when we shut down completely so that the cache is cleared.

      To us the only conclusion that we can draw as remote developers is that there is some difference between our hardware that we cannot identify.  We have now talked over the phone with reps from both North America and Filemaker UK and the initial response from both when discussing the issue is that there has to be something different in the hardware/environment that is preventing the system from running.

      We are attempting to work out the hardware issues with the party that handles that for the client, but he has told us point blank that our speculations about the differences in hardware are ridiculous.  We are at a loss for what to do here.

      Has anyone experienced anything like this?  Can you provide some input on how best to resolve this issue?  Or can someone provide an explanation as to why this is happening?

      We can provide Filemaker with everything from actual files, video, full hardware specs., etc.