[FX.php List] Web traffic versus native FileMaker use

Joel Shapiro jsfmp at earthlink.net
Fri May 7 09:27:56 MDT 2010


Hi Jon

Like Dale, the FM DB in my situation was created/maintained by another  
FM developer.  Once I told him the cause of the web slowness, he  
commented out the auto-enter calcs and the web-based record creation  
was back to almost immediate.  This was less than 48 hrs ago so we  
don't yet have a working solution to replace the auto-enter calcs, but  
he's suggested running an FM script right after the new-record call  
from PHP.  I'm still waiting on some details about it from him before  
I set it up, but I can report back once it's done.

I'd say that if you're not sure that the auto-enter calcs are the  
cause of your delays, you might want to try just temporarily  
commenting them out to see if that makes a difference.

Best,
-Joel


On May 6, 2010, at 7:34 PM, Jon & Jane Montgomery wrote:

> On the subject of these offending auto-entry calc fields, what did  
> you guys
> do to elemanate the congestion?  I have some auto-entry calc fields on
> record creation on a database that gets very slow.  I would like to  
> fix that
> if you can be of help.
>
> Respectfully,
>
> Jon Montgomery
>
>
> On 5/6/10 6:54 PM, "Joel Shapiro" <jsfmp at earthlink.net> wrote:
>
>> Just a "me too" to auto-enter calcs that were not on my web layout  
>> but
>> still causing huge delays.
>>
>> -Joel
>>
>>
>> On May 6, 2010, at 4:49 PM, Dale Bengston wrote:
>>
>>> Good stuff, Chris.
>>>
>>> Since the topic of optimizing web layouts came up here and in one
>>> other post today, I will restate that my problems with record
>>> creation had to do with two auto-enter calc fields. The two
>>> offending auto-enter calc fields were among the 368 fields that were
>>> *not* on my web layout. This took me a long time to diagnose,
>>> because I knew my layout was completely stripped of all but the ten
>>> or so fields needed for the web.
>>>
>>> Dale
>>>
>>> On May 6, 2010, at 6:31 PM, Chris Hansen wrote:
>>>
>>>> Jonathan,
>>>>
>>>> A few thoughts:
>>>>
>>>> 1) Does the deployment use IWP at all?  IWP will eat up one of your
>>>> 100 available connections for each person connected, even if
>>>> they're not doing anything;
>>>>
>>>> 2) Are there unstored calcs or summary fields on any web layouts?
>>>>
>>>> 3) Does the database have a close script, and if so, what does it
>>>> look like?  Just a while ago the WPE used to run the database's
>>>> close script on EVERY connection.  I'm not sure if this has been
>>>> fixed.  At the very least, this is something you could test for...
>>>>
>>>> 4) What is the network connection like?  I wondering if the right
>>>> (wrong?) setup and/or a bad port might show its presence in this
>>>> way...  (Not sure about this, but I know from experience that
>>>> hardware problems can manifest themselves in interesting ways...)
>>>>
>>>> Best,
>>>>
>>>> --Chris
>>>>
>>>> On May 6, 2010, at 12:21 PM, Jonathan Schwartz wrote:
>>>>
>>>>> Hi Folks,
>>>>>
>>>>> I'm wondering if anyone has experience with the negative impact of
>>>>> native FileMaker use on the same db/hardware/network etc that is
>>>>> used by php-based web users (fx.php/API/etc).
>>>>>
>>>>> In short, I am trying to get to the bottom of severe web
>>>>> performance degradation during the day, as web transactions that
>>>>> normally take 0.1 second to perform will jump to 30  seconds or
>>>>> more.
>>>>>
>>>>> I suspect that scripts running in native FileMaker are the
>>>>> culprit. The environment is FMS 10 in a 2 machine deployment.
>>>>> There are 10-20 native FileMaker users logged in on average. The
>>>>> hardware is Windows and the Task Manager(s) show the machines
>>>>> idling at all times...even during these overload times.  Perhaps I
>>>>> am not looking at the right indicators.
>>>>>
>>>>> My first move to isolate the problem was to move the web-based
>>>>> data tables into a separate file from the one the native FileMaler
>>>>> users access. That didn't help much. The files still share the
>>>>> same hardware.
>>>>>
>>>>> My next moves could include:
>>>>> - spin the web file to different hard drive/same machine
>>>>> - spin the web operation to different server
>>>>> - spin the web operation to different server at a different
>>>>> location.
>>>>>
>>>>> Anyone?
>>>>>
>>>>> Jonathan
>>>>> -- 
>>>>> Jonathan Schwartz
>>>>> Exit 445 Group
>>>>> jonathan at exit445.com
>>>>> http://www.exit445.com
>>>>> 415-370-5011
>>>>> _______________________________________________
>>>>> FX.php_List mailing list
>>>>> FX.php_List at mail.iviking.org
>>>>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>>>>
>>>>
>>>> _______________________________________________
>>>> FX.php_List mailing list
>>>> FX.php_List at mail.iviking.org
>>>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>>
>>> _______________________________________________
>>> FX.php_List mailing list
>>> FX.php_List at mail.iviking.org
>>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list



More information about the FX.php_List mailing list