[FX.php List] can only create 4 records before timeout
Gjermund Gusland Thorsen
ggt667 at gmail.com
Thu Aug 6 12:05:30 MDT 2009
One of the larger solutions I help support has its own web.fp7 file it
only has 2 tables weblog and weberrors
The weblog logs all actions of the webusers and barcode users.
The weberrors logs every time an errorCode != 0
The rest of that file a layouts from other databases, instansciated in
the web.fp7 graph.
It helps speed to make one layout for each purpose
xmlLogin
xmlControlPanelUserData
xmlControlPanelSignatureData
xmlControlPanelIMData
xmlForumMessage
and so on
The following 3: xmlControlPanelUserData,
xmlControlPanelSignatureData, xmlControlPanelIMData would most likely
be 3 layouts with different field selections from the same table.
ggt667
2009/8/6 David Cox <davidcox at wcfs.edu>:
> Jonathan, Chris, Leo, Gjermund and anyone else who helped me out:
>
> Your help has been immensely appreciated. I was finally able to do what I
> wanted without the timeout by creating a separate related table. Now that I
> am working with a much smaller related table, the script flies!
>
> What had me baffled is that the timeout still happened when using a layout
> with only two or three fields. All I can think is that there are a large
> number of calculation fields in that table which derive data from other
> relationships and/or other fields in the table. Even though I was only
> dealing with two or three fields on the layout, FileMaker must have still
> been doing background work when the record was created.
>
> On a separate topic, Dale Bengston mentioned about storing form data into
> the session and then writing it at a later point. Although I use session
> variables extensively, I've never thought of using the session as the
> endpoint for the data storage as a virtual database and then committing it
> to FileMaker in the background when it has the time. If fully developed and
> implemented, I think this concept has potential to make web apps fly, reduce
> workload on FileMaker and turn FileMaker into a data repository which is
> only accessed at initial login and on logout when the user is finished
> making changes. I can see how this would radically change the way php
> interfaces with FileMaker but would also have many potential pitfalls. One
> would need to make sure that data is indeed written to the database and not
> discarded by PHP if the user drops off. It would also change the real time
> interface of PHP with FileMaker - which for many purposes would not matter
> as long as the data does make it back into FileMaker. Another problem is
> that one would not be able to take advantage of the FileMaker relational
> capabilities - however FileMaker could be accessed as needed, but not as
> much. Am I getting a little carried away with this idea?
>
> @ Jonathan: You mentioned about logging time information to a server file.
> Do you have any sample scripts which I could refer to?
>
>
> Thank you all for your help,
> David Cox
>
>
>
>
>
> On Sat, Aug 1, 2009 at 12:16 PM, <fx.php_list-request at mail.iviking.org>
> wrote:
>>
>> Send FX.php_List mailing list submissions to
>> fx.php_list at mail.iviking.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>> or, via email, send a message with subject or body 'help' to
>> fx.php_list-request at mail.iviking.org
>>
>> You can reach the person managing the list at
>> fx.php_list-owner at mail.iviking.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of FX.php_List digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: can only create 4 records before timeout
>> (Gjermund Gusland Thorsen)
>> 2. Re: can only create 4 records before timeout
>> (Gjermund Gusland Thorsen)
>> 3. Re: Shopping Carts - Keep in SessionVars or Add Recordsright
>> away? (Dale Bengston)
>> 4. Re: can only create 4 records before timeout (Jonathan Schwartz)
>> 5. Re: can only create 4 records before timeout (Chris Hansen)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 30 Jul 2009 00:46:46 +0200
>> From: Gjermund Gusland Thorsen <ggt667 at gmail.com>
>> Subject: Re: [FX.php List] can only create 4 records before timeout
>> To: "FX.php Discussion List" <fx.php_list at mail.iviking.org>
>> Message-ID:
>> <e6ecb7940907291546i6fadd207q9295592f83adbcd6 at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> I name them xmlPurpose
>>
>> ggt
>>
>> 2009/7/30 Leo R. Lundgren <leo at finalresort.org>:
>> > I always use seperate layouts for FX/FMPHPAPI, containing only the
>> > needed
>> > fields without any extra candy. I suffix them with " | XML" but
>> > otherwise
>> > they're named the same as the "normal layouts", so that they're easy to
>> > track.
>> >
>> >
>> > 29 jul 2009 kl. 23.52 skrev Jonathan Schwartz:
>> >
>> >> First things first.
>> >>
>> >> - Reduce layout fields to just those needed for this script.
>> >>
>> >> - increase timeout setting in php, either in ini or with an ini set
>> >> command in the script.
>> >>
>> >> - Add some logging that tells you where the time is being spent. You
>> >> have
>> >> to log to a file instead if the screen because nothing gets written to
>> >> the
>> >> screen until the script finishes. And if the browser times out you get
>> >> nada.
>> >>
>> >> Hth.
>> >>
>> >>
>> >>
>> >> Jonathan Schwartz
>> >> Exit 445 Group
>> >> 415-370-5011
>> >>
>> >> On Jul 29, 2009, at 2:22 PM, Troy Meyers <tcmeyers at troymeyers.com>
>> >> wrote:
>> >>
>> >>> David,
>> >>>
>> >>> If the layout you are referring to during creation has all 200 fields
>> >>> (or
>> >>> even just more than you need), then I'd definitely try your option
>> >>> (2.)
>> >>> first. Here I have many layouts for different purposes, and putting
>> >>> only the
>> >>> fields needed to accomplish the purpose makes great speed
>> >>> improvements.
>> >>>
>> >>> -Troy
>> >>>
>> >>>
>> >>>
>> >>>> I am using a loop to create records when they do not exist. As I
>> >>>> stated
>> >>>> yesterday, it only gets four records created before timeout.
>> >>>>
>> >>>> IIS 6 & the FM7 WPE is on a dedicated Win2K3 server. FileMaker
>> >>>> Server 7
>> >>>> is on an adjacent Win2K3 server and both are connected via a local
>> >>>> gigabit switch and both are dual processors with adequate RAM. I am
>> >>>> trying to find out what is causing the performance hit or latency
>> >>>> issues. I can monitor both servers' processor & network %usage and
>> >>>> it
>> >>>> appears that the FM7 Server is doing some significant number
>> >>>> crunching
>> >>>> over the processor when I run the script.
>> >>>>
>> >>>> Should I try:
>> >>>>
>> >>>> 1. moving FileMaker Server onto the same hardware?
>> >>>>
>> >>>> 2. performing the FMNew() on a layout with just a few fields?
>> >>>>
>> >>>> 3. upgrading to a newer version of FileMaker Server? (is there any
>> >>>>
>> >>>> increase in performance in 9 or 10? I am certain FileMaker will tell
>> >>>> me
>> >>>>
>> >>>> that I need to upgrade. However budget precludes that possibility
>> >>>> for
>> >>>> now)
>> >>>>
>> >>>> 4. reducing the number of fields and or relationships in the
>> >>>> database?
>> >>>>
>> >>>> The table I am working in has over 200 fields.
>> >>>>
>> >>>> Any ideas?
>> >>>>
>> >>>> Thanks,
>> >>>>
>> >>>> David Cox
>> >>>
>> >>> _______________________________________________
>> >>> 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
>> >
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 30 Jul 2009 00:47:30 +0200
>> From: Gjermund Gusland Thorsen <ggt667 at gmail.com>
>> Subject: Re: [FX.php List] can only create 4 records before timeout
>> To: "FX.php Discussion List" <fx.php_list at mail.iviking.org>
>> Message-ID:
>> <e6ecb7940907291547g558b56b6n7ef7c582ad563228 at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> With FileMaker 5/6 i used the name of the php script that used that
>> laoyut.
>>
>> ggt
>>
>> 2009/7/30 Gjermund Gusland Thorsen <ggt667 at gmail.com>:
>> > I name them xmlPurpose
>> >
>> > ggt
>> >
>> > 2009/7/30 Leo R. Lundgren <leo at finalresort.org>:
>> >> I always use seperate layouts for FX/FMPHPAPI, containing only the
>> >> needed
>> >> fields without any extra candy. I suffix them with " | XML" but
>> >> otherwise
>> >> they're named the same as the "normal layouts", so that they're easy to
>> >> track.
>> >>
>> >>
>> >> 29 jul 2009 kl. 23.52 skrev Jonathan Schwartz:
>> >>
>> >>> First things first.
>> >>>
>> >>> - Reduce layout fields to just those needed for this script.
>> >>>
>> >>> - increase timeout setting in php, either in ini or with an ini set
>> >>> command in the script.
>> >>>
>> >>>
>> >>> Hth.
>> >>>
>> >>>
>> >>>
>> >>> Jonathan Schwartz
>> >>> Exit 445 Group
>> >>> 415-370-5011
>> >>>
>> >>> On Jul 29, 2009, at 2:22 PM, Troy Meyers <tcmeyers at troymeyers.com>
>> >>> wrote:
>> >>>
>> >>>> David,
>> >>>>
>> >>>> If the layout you are referring to during creation has all 200 fields
>> >>>> (or
>> >>>> even just more than you need), then I'd definitely try your option
>> >>>> (2.)
>> >>>> first. Here I have many layouts for different purposes, and putting
>> >>>> only the
>> >>>> fields needed to accomplish the purpose makes great speed
>> >>>> improvements.
>> >>>>
>> >>>> -Troy
>> >>>>
>> >>>>
>> >>>>
>> >>>>> I am using a loop to create records when they do not exist. As I
>> >>>>> stated
>> >>>>> yesterday, it only gets four records created before timeout.
>> >>>>>
>> >>>>> IIS 6 & the FM7 WPE is on a dedicated Win2K3 server. FileMaker
>> >>>>> Server 7
>> >>>>> is on an adjacent Win2K3 server and both are connected via a local
>> >>>>> gigabit switch and both are dual processors with adequate RAM. I am
>> >>>>> trying to find out what is causing the performance hit or latency
>> >>>>> issues. I can monitor both servers' processor & network %usage and
>> >>>>> it
>> >>>>> appears that the FM7 Server is doing some significant number
>> >>>>> crunching
>> >>>>> over the processor when I run the script.
>> >>>>>
>> >>>>> Should I try:
>> >>>>>
>> >>>>> 1. moving FileMaker Server onto the same hardware?
>> >>>>>
>> >>>>> 2. performing the FMNew() on a layout with just a few fields?
>> >>>>>
>> >>>>> 3. upgrading to a newer version of FileMaker Server? (is there any
>> >>>>>
>> >>>>> increase in performance in 9 or 10? I am certain FileMaker will tell
>> >>>>> me
>> >>>>>
>> >>>>> that I need to upgrade. However budget precludes that possibility
>> >>>>> for
>> >>>>> now)
>> >>>>>
>> >>>>> 4. reducing the number of fields and or relationships in the
>> >>>>> database?
>> >>>>>
>> >>>>> The table I am working in has over 200 fields.
>> >>>>>
>> >>>>> Any ideas?
>> >>>>>
>> >>>>> Thanks,
>> >>>>>
>> >>>>> David Cox
>> >>>>
>> >>>> _______________________________________________
>> >>>> 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
>> >>
>> >
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Wed, 29 Jul 2009 20:30:37 -0500
>> From: Dale Bengston <dbengston at tds.net>
>> Subject: Re: [FX.php List] Shopping Carts - Keep in SessionVars or Add
>> Recordsright away?
>> To: "FX.php Discussion List" <fx.php_list at mail.iviking.org>
>> Message-ID: <022784FF-351D-40D2-BF17-5B6477E0F7EA at tds.net>
>> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed;
>> delsp=yes
>>
>> I would expect storage of form data in $_SESSION to be faster than
>> storing it in FileMaker tables. Storing anything in memory is faster
>> than writing it out, especially if your target for writing is
>> FileMaker. The marginal speed trade-off of writing records is
>> acceptable to me... especially since I rarely find myself writing to
>> FileMaker any more. (Yes, I know. Sniff. Sniff.)
>>
>> Dale
>>
>> On Jul 29, 2009, at 2:58 PM, Leo R. Lundgren wrote:
>>
>> > There is definately a time difference. Unless I misunderstood what
>> > you mean by session variables.
>> >
>> > If you just write thirty variables to the $_SESSION array, there
>> > only overhead involved is the one when PHP seralizes the values into
>> > the session storage, which by default is files under /tmp on the
>> > webserver. But this is isn't noticable for low-traffic hosts.
>> >
>> > On the other hand, if you are to write your values to a table in
>> > FileMaker, you have all the usual overhead involved with
>> > communicating with said database.
>> >
>> >
>> > 29 jul 2009 kl. 20.45 skrev Bob Patin:
>> >
>> >> Here's a question for GGT (or anyone else who may know this): is
>> >> there any speed difference at all between writing 30 or so session
>> >> variables versus writing 30 or so fields to 1 or more tables?
>> >>
>> >> For the sake of argument, let's say you're writing to two tables--
>> >> first is the temp order table, 2nd is the lineitems table.
>> >>
>> >> Is the difference in time involved negligible?
>> >>
>> >> Best,
>> >>
>> >> Bob Patin
>> >>
>> >>
>> >> <new_logo_idea3_120w.jpg>
>> >>
>> >>
>> >>
>> >> Longterm Solutions
>> >> bob at longtermsolutions.com
>> >> 615-333-6858
>> >> http://www.longtermsolutions.com
>> >> iChat: bobpatin
>> >> FileMaker 10 Certified Developer
>> >> Member of FileMaker Business Alliance and FileMaker TechNet
>> >> --------------------------
>> >> FileMaker hosting and consulting for all versions of FileMaker
>> >> PHP • Full email services • Free DNS hosting • Colocation •
>> >> Consulting
>> >>
>> >> On Jul 29, 2009, at 12:43 PM, Joel Shapiro wrote:
>> >>
>> >>> Don't know how long this thread may keep going, but let me put in
>> >>> my "Thanks Everybody" here & now:
>> >>>
>> >>> Thanks Everybody
>> >>>
>> >>> Best,
>> >>> -Joel
>> >>>
>> >>> ~~~~~~~~~~~~~~~~~~~~~~~
>> >>> Joel Shapiro
>> >>> FileMaker Pro
>> >>> database & web design
>> >>> http://www.jsfmp.com
>> >>> 415-269-5055
>> >>> ~~~~~~~~~~~~~~~~~~~~~~~
>> >>>
>> >>>
>> >>> On Jul 29, 2009, at 9:43 AM, VanBuskirk, Patricia wrote:
>> >>>
>> >>>> As a frequent online shopper, I like this idea. I had over $100 of
>> >>>> merch in my cart at Khols online, accumulated throughout the day,
>> >>>> and I
>> >>>> went away from my pc for a couple of hours to come back to an empty
>> >>>> cart. I did not try to re-shop, so they lost the business.
>> >>>>
>> >>>>
>> >>>> -----Original Message-----
>> >>>> From: fx.php_list-bounces at mail.iviking.org
>> >>>> [mailto:fx.php_list-bounces at mail.iviking.org] On Behalf Of Dale
>> >>>> Bengston
>> >>>> Sent: Wednesday, July 29, 2009 12:37 PM
>> >>>> To: FX.php Discussion List
>> >>>> Subject: Re: [FX.php List] Shopping Carts - Keep in SessionVars
>> >>>> or Add
>> >>>> Recordsright away?
>> >>>>
>> >>>> I agree that this is a client business rule, but there is very
>> >>>> little
>> >>>> penalty for saving records to a table, and keeping them as a status
>> >>>> that is suppressed by the client-server UI. I am doing this for an
>> >>>> order site. In my opinion, saving records also makes it easier to
>> >>>> retrieve a shopping cart if the user quits and relaunches, or in
>> >>>> another typical, natural way destroys their session.
>> >>>>
>> >>>> Dale
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Dale Bengston
>> >>>> Streamline Studio, LLC
>> >>>> www.streamline-studio.com
>> >>>>
>> >>>> On Jul 29, 2009, at 10:46 AM, Bob Patin wrote:
>> >>>>
>> >>>>> For one client it was a half-hour; this wasn't a cart per se,
>> >>>>> but a
>> >>>>> registration site. The issue for the client was to make sure that
>> >>>>> everyone who completed the process was definitely sent an email
>> >>>>> confirmation; eventually the other programmer in this project (I
>> >>>>> was
>> >>>>> a sub-contractor on this) decided to write a script, and trigger
>> >>>>> it
>> >>>>> every 60 seconds. It looks for abandoned registrations, and if
>> >>>>> it's
>> >>>>> been more than a half-hour, deletes the temp record. If not, it
>> >>>>> confirms that there's a credit card payment auth code and if so,
>> >>>>> it
>> >>>>> sends the confirmation email.
>> >>>>>
>> >>>>> I don't use scripts much at all in web apps, but this was what the
>> >>>>> other consultant wanted, and it does work pretty well with
>> >>>>> scheduled
>> >>>>> script-triggering from Server 10.
>> >>>>>
>> >>>>> For this app we use a temp table, but for a smaller app on the
>> >>>>> same
>> >>>>> site, where people are signing up for meetings, I store everything
>> >>>>> in session variables until the end because there's not much to
>> >>>>> keep
>> >>>>> track of...
>> >>>>>
>> >>>>> BP
>> >>>>>
>> >>>>> Bob Patin
>> >>>>> Longterm Solutions LLC
>> >>>>> bob at longtermsolutions.com
>> >>>>> 615-333-6858
>> >>>>> http://www.longtermsolutions.com
>> >>>>> Twitter: bobpatin
>> >>>>> iChat/AIM: bobpatin
>> >>>>> FileMaker 10 Certified Developer
>> >>>>> Member of FileMaker Business Alliance & TechNet
>> >>>>> --------------------------
>> >>>>> FileMaker hosting and consulting for all versions of FileMaker
>> >>>>> PHP * jQuery * ExpressionEngine
>> >>>>> Full email services * Free DNS hosting * Colocation * Consulting
>> >>>>>
>> >>>>>
>> >>>>> On Jul 29, 2009, at 3:49 AM, Gjermund Gusland Thorsen wrote:
>> >>>>>
>> >>>>>> What are your criterias for deleting the carts not owned by
>> >>>>>> anybody?
>> >>>>>>
>> >>>>>> ggt
>> >>>>>>
>> >>>>>> 2009/7/29 Head Honcho <headhoncho at customikesolutions.com>:
>> >>>>>>> Hi Joel,
>> >>>>>>>
>> >>>>>>> I record them immediately, and run a script weekly to "delete"
>> >>>>>>> non
>> >>>>>>> purchased
>> >>>>>>> orders.
>> >>>>>>>
>> >>>>>>> It also helps in the reporting to see what people have started
>> >>>>>>> ordering and
>> >>>>>>> then dropped out, so to speak.
>> >>>>>>>
>> >>>>>>> As Webko said, this also allows for "pausing" an order and
>> >>>>>>> resuming it
>> >>>>>>> later.
>> >>>>>>>
>> >>>>>>> HTH.
>> >>>>>>>
>> >>>>>>> Regards
>> >>>>>>>
>> >>>>>>> Michael Ward
>> >>>>>>> --
>> >>>>>>> Head Honcho
>> >>>>>>> CustoMike Solutions
>> >>>>>>> Member, FileMaker Business Alliance
>> >>>>>>> Member, FileMaker Technical Network
>> >>>>>>> FileMaker 7 Certified Developer
>> >>>>>>> FileMaker 8 Certified Developer
>> >>>>>>> FileMaker 9 Certified Developer
>> >>>>>>> FileMaker 10 Certified Developer
>> >>>>>>> 10 Wandoo Crt
>> >>>>>>> Wheelers Hill, 3150
>> >>>>>>> ph 0414 562 501
>> >>>>>>> headhoncho at customikesolutions.com
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> On 29/07/2009, at 9:24 AM, Joel Shapiro wrote:
>> >>>>>>>
>> >>>>>>>> Thanks Leo
>> >>>>>>>>
>> >>>>>>>> That's what I'd been thinking.
>> >>>>>>>>
>> >>>>>>>> It's good to see what different people are doing...
>> >>>>>>>>
>> >>>>>>>> -Joel
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> On Jul 28, 2009, at 4:18 PM, Leo R. Lundgren wrote:
>> >>>>>>>>
>> >>>>>>>>> Yeah there's really a question of what features you want.
>> >>>>>>>>>
>> >>>>>>>>> The basic approach is to keep the cart in the session as
>> >>>>>>>>> session
>> >>>>>>>>> variables. There's really no need to put it all in the
>> >>>>>>>>> database,
>> >>>>>>>>> use the
>> >>>>>>>>> session for what it's worth instead :)
>> >>>>>>>>>
>> >>>>>>>>> BUT, keeping the cart inside the DB will allow for certain
>> >>>>>>>>> things, such
>> >>>>>>>>> as the client can put some stuff in the cart, mail his
>> >>>>>>>>> collegue,
>> >>>>>>>>> and tell
>> >>>>>>>>> him "hey, look at the stuff I put in our cart", and the
>> >>>>>>>>> collegue
>> >>>>>>>>> can do so
>> >>>>>>>>> from a totally different computer. They can collaborate.
>> >>>>>>>>>
>> >>>>>>>>> If that latter example isn't needed, I'd store it in the
>> >>>>>>>>> session.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> 29 jul 2009 kl. 01.14 skrev Tim 'Webko' Booth:
>> >>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On 29/07/2009, at 9:11 AM, Joel Shapiro wrote:
>> >>>>>>>>>>
>> >>>>>>>>>>> Hi all
>> >>>>>>>>>>>
>> >>>>>>>>>>> Anybody have any thoughts on *when* in shopping cart
>> >>>>>>>>>>> functionality it's
>> >>>>>>>>>>> best to add items as records to the database?
>> >>>>>>>>>>>
>> >>>>>>>>>>> My initial thinking is that it would make more sense to just
>> >>>>>>>>>>> keep items
>> >>>>>>>>>>> in Session Variable arrays and only add anything to the
>> >>>>>>>>>>> database at the time
>> >>>>>>>>>>> of Checkout -- to keep the DB from bulking up with
>> >>>>>>>>>>> unpurchased
>> >>>>>>>>>>> items left in
>> >>>>>>>>>>> the cart. But searching online, it seems that carts often
>> >>>>>>>>>>> add
>> >>>>>>>>>>> records to
>> >>>>>>>>>>> the database as soon as they go into the cart. (Might
>> >>>>>>>>>>> that be
>> >>>>>>>>>>> different
>> >>>>>>>>>>> when using MySQL as opposed to FMP?)
>> >>>>>>>>>>>
>> >>>>>>>>>>> FWIW - Users on this site will average 1-4 items per order.
>> >>>>>>>>>>
>> >>>>>>>>>> I tend to add them immediately - allows me to also re-show
>> >>>>>>>>>> previous not
>> >>>>>>>>>> actually purchased items on request further down the track...
>> >>>>>>>>>>
>> >>>>>>>>>> Cheers
>> >>>>>>>>>>
>> >>>>>>>>>> Webko
>> >>>>>>>>>> _______________________________________________
>> >>>>>>>>>> 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
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> 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
>> >
>> >
>> > -|
>> >
>> > _______________________________________________
>> > FX.php_List mailing list
>> > FX.php_List at mail.iviking.org
>> > http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Fri, 31 Jul 2009 08:50:24 -0700
>> From: Jonathan Schwartz <jschwartz at exit445.com>
>> Subject: Re: [FX.php List] can only create 4 records before timeout
>> To: "FX.php Discussion List" <fx.php_list at mail.iviking.org>
>> Message-ID: <p0620070bc698c310a794@[192.168.1.102]>
>> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>>
>> How did that work out for you, David?
>>
>> Jonathan
>> --
>> Jonathan Schwartz
>> Exit 445 Group
>> jonathan at exit445.com
>> http://www.exit445.com
>> 415-370-5011
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Sat, 1 Aug 2009 10:16:50 -0600
>> From: Chris Hansen <chris at iViking.org>
>> Subject: Re: [FX.php List] can only create 4 records before timeout
>> To: "FX.php Discussion List" <fx.php_list at mail.iviking.org>
>> Message-ID: <C28D9783-DFA7-4671-84A8-CE0567006DA6 at iViking.org>
>> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>>
>> David,
>>
>> Jonathan is right on track. Unstored calcs and summary fields
>> especially can add time. Be sure you ONLY have the fields on there
>> that you need.
>>
>> Another thought: you could create the records one at a time, but only
>> populate (and use a layout) with one or two fields, and then use
>> another layout with a portal to edit all of those records with a
>> single query. This may even be a situation where using a FileMaker
>> script (as opposed to doing everything with PHP) would make sense.
>>
>> Note that there are two keys here:
>>
>> 1) FileMaker does the work for all of the fields on any layout you
>> use, whether you do anything with the returned data or not;
>>
>> 2) There is a fair amount of overhead involved with informational XML
>> (header information, if you will) returned for each XML query, so the
>> fewer the queries the better (FYI, the FileMaker API for PHP uses an
>> even MORE verbose schema...)
>>
>> HTH
>>
>> --Chris
>>
>> On Jul 29, 2009, at 3:52 PM, Jonathan Schwartz wrote:
>>
>> > First things first.
>> >
>> > - Reduce layout fields to just those needed for this script.
>> >
>> > - increase timeout setting in php, either in ini or with an ini set
>> > command in the script.
>> >
>> > - Add some logging that tells you where the time is being spent. You
>> > have to log to a file instead if the screen because nothing gets
>> > written to the screen until the script finishes. And if the browser
>> > times out you get nada.
>> >
>> > Hth.
>> >
>> >
>> >
>> > Jonathan Schwartz
>> > Exit 445 Group
>> > 415-370-5011
>> >
>> > On Jul 29, 2009, at 2:22 PM, Troy Meyers <tcmeyers at troymeyers.com>
>> > wrote:
>> >
>> >> David,
>> >>
>> >> If the layout you are referring to during creation has all 200
>> >> fields (or even just more than you need), then I'd definitely try
>> >> your option (2.) first. Here I have many layouts for different
>> >> purposes, and putting only the fields needed to accomplish the
>> >> purpose makes great speed improvements.
>> >>
>> >> -Troy
>> >>
>> >>
>> >>
>> >>> I am using a loop to create records when they do not exist. As I
>> >>> stated
>> >>> yesterday, it only gets four records created before timeout.
>> >>>
>> >>> IIS 6 & the FM7 WPE is on a dedicated Win2K3 server. FileMaker
>> >>> Server 7
>> >>> is on an adjacent Win2K3 server and both are connected via a local
>> >>> gigabit switch and both are dual processors with adequate RAM. I am
>> >>> trying to find out what is causing the performance hit or latency
>> >>> issues. I can monitor both servers' processor & network %usage
>> >>> and it
>> >>> appears that the FM7 Server is doing some significant number
>> >>> crunching
>> >>> over the processor when I run the script.
>> >>>
>> >>> Should I try:
>> >>>
>> >>> 1. moving FileMaker Server onto the same hardware?
>> >>>
>> >>> 2. performing the FMNew() on a layout with just a few fields?
>> >>>
>> >>> 3. upgrading to a newer version of FileMaker Server? (is there any
>> >>>
>> >>> increase in performance in 9 or 10? I am certain FileMaker will tell
>> >>> me
>> >>>
>> >>> that I need to upgrade. However budget precludes that possibility
>> >>> for
>> >>> now)
>> >>>
>> >>> 4. reducing the number of fields and or relationships in the
>> >>> database?
>> >>>
>> >>> The table I am working in has over 200 fields.
>> >>>
>> >>> Any ideas?
>> >>>
>> >>> Thanks,
>> >>>
>> >>> David Cox
>> >>
>> >> _______________________________________________
>> >> 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
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>> End of FX.php_List Digest, Vol 61, Issue 1
>> ******************************************
>
>
> _______________________________________________
> 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