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

[Dale Bengston]

Hi Jonathan,

I'll bite. This happened to me when I put a web UI on another developer's FMP client/server installation. Creation of an order line item started to take longer and longer, until the point of absurdity. I finally traced it to some calc fields used by the client/server UI, that summarized data. (Running totals, etc.) In the client/server environment, values of constants/global fields made sure those line items were only summarized for the current found set (i.e. the invoice you were viewing). But on the web, the entire table was getting summarized. Once the number of line items got in the thousands, web performance went into the tank. This problem did not manifest itself during testing, when there were just a few test invoices at any given time. Note that these fields were not on any layouts used by the web. They were calculated on record creation.

My problem was based on volume of records, rather than time of day, but maybe my experience will help you triangulate. Does your performance get better with fewer clients logged in? What kind of ongoing client/server scripts are running, even when clients are idle?

Hope this helps,
Dale

On May 6, 2010, at 1: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