[FX.php List] Performance hit for unpopulated fields on layouts?

[Dale Bengston]

You're absolutely right - it all depends. If you're only pulling one  
record from FMP each time, or usage is light, you'll probably be  
okay. Also, a lot of it has to do with user expectations. If they've  
never used it any faster than it is, and your pages load with  
reasonable speed (compared to their perceptions of other sites), then  
it will be fine.

My partner and I have recently set up our "framework" so we can  
toggle a site between MySQL and FileMaker (using FX.php) by resetting  
a single variable/constant. This allows us the comfort of developing  
and prototyping in FMP, but the flexibility to deploy on MySQL. The  
MySQL support of FX has not been entirely consistent with FMP  
support, but we're working around that and hoping for some  
improvements in the next release of FX.

Dale

On Aug 25, 2007, at 9:52 AM, Jonathan Schwartz wrote:

> Thanks Dale,
>
> Of course, it depends.  But I would guess that it would be closer  
> to 50 with up to half not used.
>
> I'm going to give it a try and see what happens...with an open mind  
> toward migrating to MySQL.
>
> If this project pans out, it would have to scale up anyway.
>
> Thanks
>
> J
>
>
> At 11:41 PM -0500 8/24/07, Dale Bengston wrote:
>> Hi Jonathan,
>>
>> Even un-populated fields add overhead to the data being pulled  
>> from a layout. How many fields total? Are we talking 100 or 10,  
>> half of which would be empty?
>>
>> MySQL does not have the same "problem," because the data pulled  
>> from MySQL is not tied to a physical layout like it is with  
>> FileMaker.
>>
>> Dale
>>
>> On Aug 24, 2007, at 9:43 PM, Jonathan Schwartz wrote:
>>
>>> Hi Folks,
>>>
>>> I'm working on a project where I will allow clients to build  
>>> their own fx.php powered web pages by having them selecting from  
>>> a list of available fmp fields in a database.  In order to  
>>> provide flexibility, there might be twice as many fields on a  
>>> layout than the user might select.  The system will then build  
>>> the fx.php page from the selected fields. The unused fields would  
>>> remain on the layout.
>>>
>>> The question I have is regarding the performance hit.  If the  
>>> unused fields remain on the layout, but stay unpopulated (no  
>>> data), would the performance suffer?
>>>
>>> Just out of curiosity, would this same scenario cause a problem  
>>> in MySQL?
>>>
>>> Thanks,
>>>
>>> Jonathan
>>>
>>>
>>>
>>>
>>> --
>>> Jonathan Schwartz
>>> Exit 445 Group
>>> jonathan at exit445.com
>>> http://www.exit445.com
>>> 415-381-1852
>>> _______________________________________________
>>> 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
>
>
> -- 
> Jonathan Schwartz
> Exit 445 Group
> jonathan at exit445.com
> http://www.exit445.com
> 415-381-1852
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list