[FX.php List] Portals in fx.php versus API

[Gjermund Gusland Thorsen]

I tend to use portal for reading, and individual FMNew()/FMEdit()
instances for each line when modifying.

ggt

2008/4/14, Gjermund Gusland Thorsen <ggt667 at gmail.com>:
> What is the main factor here is the size of the returned data, also
>  the initialization of each query should be taken into count ...
>
>  ggt
>
>  2008/4/14, Andrew Denman <adenman at tmea.org>:
>
> > I as well recall a discussion that portals were faster than multiple FX calls (especially a large number of FX calls).  I think there was someone who did a test, but this is all I could find in the archives (posted by Derrick Fogle).
>  >
>  >  ---------------------------------------
>  >  I count a transaction as every time you call FMFind(), FMNew(), i.e.
>  >  each time PHP has to ask FM for a record or recordset, and parse the
>  >  resultant XML result.
>  >
>  >  In my classic example where I can only get about a transaction per
>  >  second, I only have 2 tables: Buildings and Rooms. I was finding a
>  >  set of Buildings (about 60), and then in a foreach() loop, I was
>  >  finding for rooms in that building. Total number of transactions was
>  >  61 (one for buildings, one for rooms in each building). The average
>  >  number of room records per building is about 5-6. This 60+
>  >  transaction FX.php scenario took about a minute to load the data.
>  >
>  >  When I switched it to using a portal to Rooms from the Building
>  >  table, it was only a single transaction and although I was returning
>  >  the same total amount of data, it only took about 2 seconds to load
>  >  the data with the single transaction.
>  >
>  >  There were a couple of other instances where I was trying to do
>  >  another query inside a foreach() loop, and the difference in time
>  >  between that method and the portal method is how I arrived at my
>  >  "about 1 second per transaction" limit for my hardware.
>  >  ---------------------------------------
>  >
>  >
>  >  Andrew Denman
>  >
>  >
>  >
>  >  -----Original Message-----
>  >  From: fx.php_list-bounces at mail.iviking.org [mailto:fx.php_list-bounces at mail.iviking.org] On Behalf Of Gjermund Gusland Thorsen
>  >  Sent: Monday, April 14, 2008 3:57 PM
>  >  To: FX.php Discussion List
>  >  Subject: Re: [FX.php List] Portals in fx.php versus API
>  >
>  >  Sure is.
>  >
>  >  2008/4/14, Joel Shapiro <jsfmp at earthlink.net>:
>  >  > On Apr 14, 2008, at 11:47 AM, Dale Bengston wrote:
>  >  >
>  >  >
>  >  > > I would not do it because of the performance hit realized by retrieving
>  >  > portal data from FMP. I would retrieve the child records with a separate FX
>  >  > query.
>  >  > >
>  >  >
>  >  >  Have people done tests on this?  I'm pretty sure some people on this list
>  >  > have said that hitting the database only once, and getting all child records
>  >  > through a portal at the same time as getting the parent record, is faster.
>  >  >
>  >  >  Anybody?
>  >  >
>  >  >  -Joel
>  >  >
>  >  >  _______________________________________________
>  >  >  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
>  >
>