Ways to find cause for page delay

classic Classic list List threaded Threaded
35 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Ways to find cause for page delay

Patrick Larkin-2
Hello -

I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page I'm working on loads significantly faster with Filemaker 6(!) and am trying to track down what the issue might be.

The page simply runs one inline to pull student demographics and another inline from another database to pull a dozen other fields.  The inlines put everything into variables which are then displayed in the page using [var:'theVar'] tags.  Nothing at all unusual.

What are some techniques people use?  I tried moving the [abort] tag around but that only gets me so far.


Patrick
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Carl Ketterling
The first thing I would do is look for the amount of data that's being
returned.  Steve Piercy gave this information to me in the past:

>     [
>     inline(...);
>         $fmresults = include_url('http://mydomain/'+action_statement);
>     ]
>     <textarea>[action_statement]</textarea>
>     <textarea>[$fmresults]</textarea>
>     [
>     /inline;
>     ]

In some layouts, I was shocked to see the amount of data being returned.

Carl



In response to this text from Patrick Larkin ([hidden email])
sent on Wednesday, June 20, 2012 at 2:02 PM (-0400):

>Hello -
>
>I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>I'm working on loads significantly faster with Filemaker 6(!) and am
>trying to track down what the issue might be.
>
>The page simply runs one inline to pull student demographics and another
>inline from another database to pull a dozen other fields.  The inlines
>put everything into variables which are then displayed in the page using
>[var:'theVar'] tags.  Nothing at all unusual.
>
>What are some techniques people use?  I tried moving the [abort] tag
>around but that only gets me so far.
>
>
>Patrick
>#############################################################
>This message is sent to you because you are subscribed to
>  the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Patrick Larkin-2
I just get

/fmi/xml/FMPXMLRESULT.xml?-db= .... (and all the search criteria) in one box and the source of my 404 error page in the other box.


Patrick Larkin
Developer/Administrator of Special Systems / Webmaster
Bethlehem Area School District




On Jun 20, 2012, at 2:19 PM, Carl Ketterling wrote:

> The first thing I would do is look for the amount of data that's being
> returned.  Steve Piercy gave this information to me in the past:
>
>>    [
>>    inline(...);
>>        $fmresults = include_url('http://mydomain/'+action_statement);
>>    ]
>>    <textarea>[action_statement]</textarea>
>>    <textarea>[$fmresults]</textarea>
>>    [
>>    /inline;
>>    ]
>
> In some layouts, I was shocked to see the amount of data being returned.
>
> Carl
>
>
>
> In response to this text from Patrick Larkin ([hidden email])
> sent on Wednesday, June 20, 2012 at 2:02 PM (-0400):
>
>> Hello -
>>
>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>> I'm working on loads significantly faster with Filemaker 6(!) and am
>> trying to track down what the issue might be.
>>
>> The page simply runs one inline to pull student demographics and another
>> inline from another database to pull a dozen other fields.  The inlines
>> put everything into variables which are then displayed in the page using
>> [var:'theVar'] tags.  Nothing at all unusual.
>>
>> What are some techniques people use?  I tried moving the [abort] tag
>> around but that only gets me so far.
>>
>>
>> Patrick
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Patrick Larkin-2
Unless you are telling me to put the Filemaker Server IP as the "mydomain" in your example?

In that case, I get the source of a 401 Forbidden page.


Patrick

On Jun 20, 2012, at 2:52 PM, Patrick Larkin wrote:

> I just get
>
> /fmi/xml/FMPXMLRESULT.xml?-db= .... (and all the search criteria) in one box and the source of my 404 error page in the other box.
>
>
> Patrick Larkin
> Developer/Administrator of Special Systems / Webmaster
> Bethlehem Area School District
>
>
>
>
> On Jun 20, 2012, at 2:19 PM, Carl Ketterling wrote:
>
>> The first thing I would do is look for the amount of data that's being
>> returned.  Steve Piercy gave this information to me in the past:
>>
>>>   [
>>>   inline(...);
>>>       $fmresults = include_url('http://mydomain/'+action_statement);
>>>   ]
>>>   <textarea>[action_statement]</textarea>
>>>   <textarea>[$fmresults]</textarea>
>>>   [
>>>   /inline;
>>>   ]
>>
>> In some layouts, I was shocked to see the amount of data being returned.
>>
>> Carl
>>
>>
>>
>> In response to this text from Patrick Larkin ([hidden email])
>> sent on Wednesday, June 20, 2012 at 2:02 PM (-0400):
>>
>>> Hello -
>>>
>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>>> I'm working on loads significantly faster with Filemaker 6(!) and am
>>> trying to track down what the issue might be.
>>>
>>> The page simply runs one inline to pull student demographics and another
>>> inline from another database to pull a dozen other fields.  The inlines
>>> put everything into variables which are then displayed in the page using
>>> [var:'theVar'] tags.  Nothing at all unusual.
>>>
>>> What are some techniques people use?  I tried moving the [abort] tag
>>> around but that only gets me so far.
>>>
>>>
>>> Patrick
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Carl Ketterling
Yes, replace "mydomain" with your FileMaker Server address.

In response to this text from Patrick Larkin ([hidden email])
sent on Wednesday, June 20, 2012 at 3:01 PM (-0400):

>Unless you are telling me to put the Filemaker Server IP as the
>"mydomain" in your example?
>
>In that case, I get the source of a 401 Forbidden page.
>
>
>Patrick
>
>On Jun 20, 2012, at 2:52 PM, Patrick Larkin wrote:
>
>> I just get
>>
>> /fmi/xml/FMPXMLRESULT.xml?-db= .... (and all the search criteria) in
>one box and the source of my 404 error page in the other box.
>>
>>
>> Patrick Larkin
>> Developer/Administrator of Special Systems / Webmaster
>> Bethlehem Area School District
>>
>>
>>
>>
>> On Jun 20, 2012, at 2:19 PM, Carl Ketterling wrote:
>>
>>> The first thing I would do is look for the amount of data that's being
>>> returned.  Steve Piercy gave this information to me in the past:
>>>
>>>>   [
>>>>   inline(...);
>>>>       $fmresults = include_url('http://mydomain/'+action_statement);
>>>>   ]
>>>>   <textarea>[action_statement]</textarea>
>>>>   <textarea>[$fmresults]</textarea>
>>>>   [
>>>>   /inline;
>>>>   ]
>>>
>>> In some layouts, I was shocked to see the amount of data being returned.
>>>
>>> Carl
>>>
>>>
>>>
>>> In response to this text from Patrick Larkin ([hidden email])
>>> sent on Wednesday, June 20, 2012 at 2:02 PM (-0400):
>>>
>>>> Hello -
>>>>
>>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>>>> I'm working on loads significantly faster with Filemaker 6(!) and am
>>>> trying to track down what the issue might be.
>>>>
>>>> The page simply runs one inline to pull student demographics and another
>>>> inline from another database to pull a dozen other fields.  The inlines
>>>> put everything into variables which are then displayed in the page using
>>>> [var:'theVar'] tags.  Nothing at all unusual.
>>>>
>>>> What are some techniques people use?  I tried moving the [abort] tag
>>>> around but that only gets me so far.
>>>>
>>>>
>>>> Patrick
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>> the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>> Send administrative queries to  <[hidden email]>
>>>
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>>  the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>>
>
>#############################################################
>This message is sent to you because you are subscribed to
>  the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Tim Taplin
In reply to this post by Patrick Larkin-2
one way to get a look at what's happening throughout your page is using some simple timers, however, it sounds like your issues are likely with the Filemaker interaction and not within your lasso code.

simple timer:
get the page start time in milliseconds
        local('start' = date_msec);
Anywhere you need to know the elapsed time, output this:
        (date_msec - #start)+'ms';

by comparing the time elapsed from one code block to the next, you can see how long each piece is taking and compare results if you experiment with different layouts or methods of organizing your data and processing it.

It sounds like you may be in for some Filemaker hacking though. reviewing each layout to make sure you have layouts that use properly indexed fields, dont have extra fields on the layout that you are not retrieving, etc. If I recall correctly, Filemaker seems to benefit significantly from nested inlines, so you may want to wrap both inlines in an outer inline or just simply nest the second inline inside the first (not inside the records container ;)  ) and test to see if you get performance gains from there.

In addition, you may wish to double check the Filemaker server setup to make sure you have allowed enough resources, as the defaults are not necessarily good for web interaction.

Tim Taplin

On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:

> Hello -
>
> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page I'm working on loads significantly faster with Filemaker 6(!) and am trying to track down what the issue might be.
>
> The page simply runs one inline to pull student demographics and another inline from another database to pull a dozen other fields.  The inlines put everything into variables which are then displayed in the page using [var:'theVar'] tags.  Nothing at all unusual.
>
> What are some techniques people use?  I tried moving the [abort] tag around but that only gets me so far.
>
>
> Patrick
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Patrick Larkin-2
Thanks.  I'll try the timers since I can't seem to get Lasso to tell me the data being returned (i.e. Carl's suggestion)

The strange part is that It is roughly 3 times faster on a three server Filemaker 6 setup (web server + Filemaker Unlimited + Filemaker Server 6) with the Filemaker portion running on archaic G4 towers running 10.2.  

The new setup is web server _ Filemaker 10 Server Advanced running on a quad-core Xeon Xserve running 10.5.  The databases were converted without modification to the Filemaker 11 platform.  I expected a marked improvement just on horsepower and OS improvements alone!  :)  

Patrick Larkin
Developer/Administrator of Special Systems / Webmaster
Bethlehem Area School District




On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:

> one way to get a look at what's happening throughout your page is using some simple timers, however, it sounds like your issues are likely with the Filemaker interaction and not within your lasso code.
>
> simple timer:
> get the page start time in milliseconds
> local('start' = date_msec);
> Anywhere you need to know the elapsed time, output this:
> (date_msec - #start)+'ms';
>
> by comparing the time elapsed from one code block to the next, you can see how long each piece is taking and compare results if you experiment with different layouts or methods of organizing your data and processing it.
>
> It sounds like you may be in for some Filemaker hacking though. reviewing each layout to make sure you have layouts that use properly indexed fields, dont have extra fields on the layout that you are not retrieving, etc. If I recall correctly, Filemaker seems to benefit significantly from nested inlines, so you may want to wrap both inlines in an outer inline or just simply nest the second inline inside the first (not inside the records container ;)  ) and test to see if you get performance gains from there.
>
> In addition, you may wish to double check the Filemaker server setup to make sure you have allowed enough resources, as the defaults are not necessarily good for web interaction.
>
> Tim Taplin
>
> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>
>> Hello -
>>
>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page I'm working on loads significantly faster with Filemaker 6(!) and am trying to track down what the issue might be.
>>
>> The page simply runs one inline to pull student demographics and another inline from another database to pull a dozen other fields.  The inlines put everything into variables which are then displayed in the page using [var:'theVar'] tags.  Nothing at all unusual.
>>
>> What are some techniques people use?  I tried moving the [abort] tag around but that only gets me so far.
>>
>>
>> Patrick
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Patrick Larkin-2
In reply to this post by Tim Taplin
I put a time right after the <body> tag and got 137ms.

After displaying the results of the first inline: 6231ms.    Ludicrous.

Then twice more at 6234ms.  

I suppose this makes sense because all of the inlines execute at the beginning and then just display the fetched data which only takes 3ms.  However, since the inlines are before any HTML, are they executing in that 137ms window?  



Patrick

On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:

> one way to get a look at what's happening throughout your page is using some simple timers, however, it sounds like your issues are likely with the Filemaker interaction and not within your lasso code.
>
> simple timer:
> get the page start time in milliseconds
> local('start' = date_msec);
> Anywhere you need to know the elapsed time, output this:
> (date_msec - #start)+'ms';
>
> by comparing the time elapsed from one code block to the next, you can see how long each piece is taking and compare results if you experiment with different layouts or methods of organizing your data and processing it.
>
> It sounds like you may be in for some Filemaker hacking though. reviewing each layout to make sure you have layouts that use properly indexed fields, dont have extra fields on the layout that you are not retrieving, etc. If I recall correctly, Filemaker seems to benefit significantly from nested inlines, so you may want to wrap both inlines in an outer inline or just simply nest the second inline inside the first (not inside the records container ;)  ) and test to see if you get performance gains from there.
>
> In addition, you may wish to double check the Filemaker server setup to make sure you have allowed enough resources, as the defaults are not necessarily good for web interaction.
>
> Tim Taplin
>
> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>
>> Hello -
>>
>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page I'm working on loads significantly faster with Filemaker 6(!) and am trying to track down what the issue might be.
>>
>> The page simply runs one inline to pull student demographics and another inline from another database to pull a dozen other fields.  The inlines put everything into variables which are then displayed in the page using [var:'theVar'] tags.  Nothing at all unusual.
>>
>> What are some techniques people use?  I tried moving the [abort] tag around but that only gets me so far.
>>
>>
>> Patrick
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Carl Ketterling
Yes.  You should put a timer at the beginning and then around each inline.

Carl


In response to this text from Patrick Larkin ([hidden email])
sent on Wednesday, June 20, 2012 at 4:01 PM (-0400):

>I put a time right after the <body> tag and got 137ms.
>
>After displaying the results of the first inline: 6231ms.    Ludicrous.
>
>Then twice more at 6234ms.  
>
>I suppose this makes sense because all of the inlines execute at the
>beginning and then just display the fetched data which only takes 3ms.
>However, since the inlines are before any HTML, are they executing in
>that 137ms window?  
>
>
>
>Patrick
>
>On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:
>
>> one way to get a look at what's happening throughout your page is
>using some simple timers, however, it sounds like your issues are likely
>with the Filemaker interaction and not within your lasso code.
>>
>> simple timer:
>> get the page start time in milliseconds
>> local('start' = date_msec);
>> Anywhere you need to know the elapsed time, output this:
>> (date_msec - #start)+'ms';
>>
>> by comparing the time elapsed from one code block to the next, you can
>see how long each piece is taking and compare results if you experiment
>with different layouts or methods of organizing your data and processing it.
>>
>> It sounds like you may be in for some Filemaker hacking though.
>reviewing each layout to make sure you have layouts that use properly
>indexed fields, dont have extra fields on the layout that you are not
>retrieving, etc. If I recall correctly, Filemaker seems to benefit
>significantly from nested inlines, so you may want to wrap both inlines
>in an outer inline or just simply nest the second inline inside the
>first (not inside the records container ;)  ) and test to see if you get
>performance gains from there.
>>
>> In addition, you may wish to double check the Filemaker server setup
>to make sure you have allowed enough resources, as the defaults are not
>necessarily good for web interaction.
>>
>> Tim Taplin
>>
>> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>>
>>> Hello -
>>>
>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>I'm working on loads significantly faster with Filemaker 6(!) and am
>trying to track down what the issue might be.
>>>
>>> The page simply runs one inline to pull student demographics and
>another inline from another database to pull a dozen other fields.  The
>inlines put everything into variables which are then displayed in the
>page using [var:'theVar'] tags.  Nothing at all unusual.
>>>
>>> What are some techniques people use?  I tried moving the [abort] tag
>around but that only gets me so far.
>>>
>>>
>>> Patrick
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>>  the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>>
>
>#############################################################
>This message is sent to you because you are subscribed to
>  the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Tim Taplin
In reply to this post by Patrick Larkin-2
Are you using named inlines? or are you grabbing the data and setting to a var that you iterate thru?

If you are using the named inlines then the main overhead doesnt happen until you call it, the query is just saved until you call for the request.

May be worth putting timer inside the inline before the records loop(if you are not using named inlines) and then in each iteration of the inline records, just to get a better feel whether there's something happening in each iteration that's causing the heavy load time.

Tim Taplin

On Jun 20, 2012, at 2:01 PM, Patrick Larkin wrote:

> I put a time right after the <body> tag and got 137ms.
>
> After displaying the results of the first inline: 6231ms.    Ludicrous.
>
> Then twice more at 6234ms.  
>
> I suppose this makes sense because all of the inlines execute at the beginning and then just display the fetched data which only takes 3ms.  However, since the inlines are before any HTML, are they executing in that 137ms window?  
>
>
>
> Patrick
>
> On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:
>
>> one way to get a look at what's happening throughout your page is using some simple timers, however, it sounds like your issues are likely with the Filemaker interaction and not within your lasso code.
>>
>> simple timer:
>> get the page start time in milliseconds
>> local('start' = date_msec);
>> Anywhere you need to know the elapsed time, output this:
>> (date_msec - #start)+'ms';
>>
>> by comparing the time elapsed from one code block to the next, you can see how long each piece is taking and compare results if you experiment with different layouts or methods of organizing your data and processing it.
>>
>> It sounds like you may be in for some Filemaker hacking though. reviewing each layout to make sure you have layouts that use properly indexed fields, dont have extra fields on the layout that you are not retrieving, etc. If I recall correctly, Filemaker seems to benefit significantly from nested inlines, so you may want to wrap both inlines in an outer inline or just simply nest the second inline inside the first (not inside the records container ;)  ) and test to see if you get performance gains from there.
>>
>> In addition, you may wish to double check the Filemaker server setup to make sure you have allowed enough resources, as the defaults are not necessarily good for web interaction.
>>
>> Tim Taplin
>>
>> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>>
>>> Hello -
>>>
>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page I'm working on loads significantly faster with Filemaker 6(!) and am trying to track down what the issue might be.
>>>
>>> The page simply runs one inline to pull student demographics and another inline from another database to pull a dozen other fields.  The inlines put everything into variables which are then displayed in the page using [var:'theVar'] tags.  Nothing at all unusual.
>>>
>>> What are some techniques people use?  I tried moving the [abort] tag around but that only gets me so far.
>>>
>>>
>>> Patrick
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Carl Ketterling
In reply to this post by Carl Ketterling
Patrick,

Take your action statement and append it to this:

http://servername.domain.com/fmi/xml/FMPXMLRESULT.xml?

Paste that into your browser, and after you enter your username/
password, you'll see the XML returned by FileMaker Server.


Programmatically, that would look like this:

                var(myURL) = 'http://username:password@.../fmi/xml/
FMPXMLRESULT.xml?'+action_statement;
                var(fmresults) = include_url($myURL);

And then output $ fmresults somewhere.  I had a difficult time
displaying the XML code, so I chose the first way.  This will also
remove Lasso from the equation and you'll be able to see how fast your
server is returning the data.

Carl



In response to this text from Carl Ketterling ([hidden email]) sent on
Wednesday, June 20, 2012 at 2:31 PM (-0500):

>Yes, replace "mydomain" with your FileMaker Server address.
>
>In response to this text from Patrick Larkin ([hidden email])
>sent on Wednesday, June 20, 2012 at 3:01 PM (-0400):
>
>>Unless you are telling me to put the Filemaker Server IP as the
>>"mydomain" in your example?
>>
>>In that case, I get the source of a 401 Forbidden page.
>>
>>
>>Patrick
>>
>>On Jun 20, 2012, at 2:52 PM, Patrick Larkin wrote:
>>
>>> I just get
>>>
>>> /fmi/xml/FMPXMLRESULT.xml?-db= .... (and all the search criteria) in
>>one box and the source of my 404 error page in the other box.
>>>
>>>
>>> Patrick Larkin
>>> Developer/Administrator of Special Systems / Webmaster
>>> Bethlehem Area School District
>>>
>>>
>>>
>>>
>>> On Jun 20, 2012, at 2:19 PM, Carl Ketterling wrote:
>>>
>>>> The first thing I would do is look for the amount of data that's being
>>>> returned.  Steve Piercy gave this information to me in the past:
>>>>
>>>>>   [
>>>>>   inline(...);
>>>>>       $fmresults = include_url('http://mydomain/'+action_statement);
>>>>>   ]
>>>>>   <textarea>[action_statement]</textarea>
>>>>>   <textarea>[$fmresults]</textarea>
>>>>>   [
>>>>>   /inline;
>>>>>   ]
>>>>
>>>> In some layouts, I was shocked to see the amount of data being returned.
>>>>
>>>> Carl
>>>>
>>>>
>>>>
>>>> In response to this text from Patrick Larkin ([hidden email])
>>>> sent on Wednesday, June 20, 2012 at 2:02 PM (-0400):
>>>>
>>>>> Hello -
>>>>>
>>>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>>>>> I'm working on loads significantly faster with Filemaker 6(!) and am
>>>>> trying to track down what the issue might be.
>>>>>
>>>>> The page simply runs one inline to pull student demographics and another
>>>>> inline from another database to pull a dozen other fields.  The inlines
>>>>> put everything into variables which are then displayed in the page using
>>>>> [var:'theVar'] tags.  Nothing at all unusual.
>>>>>
>>>>> What are some techniques people use?  I tried moving the [abort] tag
>>>>> around but that only gets me so far.
>>>>>
>>>>>
>>>>> Patrick
>>>>> #############################################################
>>>>> This message is sent to you because you are subscribed to
>>>>> the mailing list Lasso
>>>>> [hidden email]
>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>> Send administrative queries to  <[hidden email]>
>>>>
>>>>
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>> the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>> Send administrative queries to  <[hidden email]>
>>>>
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>>  the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>>
>>
>>#############################################################
>>This message is sent to you because you are subscribed to
>>  the mailing list Lasso
>>[hidden email]
>>To unsubscribe, E-mail to: <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>
>
>#############################################################
>This message is sent to you because you are subscribed to
>  the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

stevepiercy
In reply to this post by Patrick Larkin-2
Patrick,

Did you provide authentication credentials within your inline?

This technique is absolutely critical to isolating the cause of
slow responses due to FM.  Don't give up on it.  See Carl's
later post.

It is not uncommon for FM >6 to run slower than FM6 in specific circumstances.

--steve


On 6/20/12 at 3:01 PM, [hidden email] (Patrick Larkin) pronounced:

>Unless you are telling me to put the Filemaker Server IP as the
>"mydomain" in your example?
>
>In that case, I get the source of a 401 Forbidden page.
>
>
>Patrick
>On Jun 20, 2012, at 2:52 PM, Patrick Larkin wrote:
>
>>I just get
>>/fmi/xml/FMPXMLRESULT.xml?-db= .... (and all the search criteria) in one box and
>the source of my 404 error page in the other box.
>>
>>
>>Patrick Larkin
>>Developer/Administrator of Special Systems / Webmaster
>>Bethlehem Area School District
>>
>>
>>
>>
>>On Jun 20, 2012, at 2:19 PM, Carl Ketterling wrote:
>>
>>> The first thing I would do is look for the amount of data that's being
>>> returned.  Steve Piercy gave this information to me in the past:
>>>
>>>>   [
>>>>   inline(...);
>>>>       $fmresults = include_url('http://mydomain/'+action_statement);
>>>>   ]
>>>>   <textarea>[action_statement]</textarea>
>>>>   <textarea>[$fmresults]</textarea>
>>>>   [
>>>>   /inline;
>>>>   ]
>>>   In some layouts, I was shocked to see the amount of data
>>>being returned.
>>>   Carl
>>>     In response to this text from Patrick Larkin ([hidden email])
>>> sent on Wednesday, June 20, 2012 at 2:02 PM (-0400):
>>>
>>>> Hello -
>>>>   I'm trying out some things with Lasso 8.6 and Filemaker
>>>>11.  The page
>>>> I'm working on loads significantly faster with Filemaker 6(!) and am
>>>> trying to track down what the issue might be.
>>>>   The page simply runs one inline to pull student
>>>>demographics and another
>>>> inline from another database to pull a dozen other fields.  The inlines
>>>> put everything into variables which are then displayed in the page using
>>>> [var:'theVar'] tags.  Nothing at all unusual.
>>>>   What are some techniques people use?  I tried moving the
>>>>[abort] tag
>>>> around but that only gets me so far.
>>>>    Patrick  #############################################################
>>>> This message is sent to you because you are subscribed to
>>>> the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>> Send administrative queries to  <[hidden email]>
>>>    #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>>
>>
>>#############################################################
>>This message is sent to you because you are subscribed to
>>the mailing list Lasso
>>[hidden email]
>>To unsubscribe, E-mail to: <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>>
>
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Patrick Larkin-2
This particular app was one of the earliest I ever built and uses the [auth_group] tag so they run the inline as themselves.  

Sent from my iPad

On Jun 20, 2012, at 7:33 PM, Steve Piercy - Web Site Builder <[hidden email]> wrote:

> Patrick,
>
> Did you provide authentication credentials within your inline?
>
> This technique is absolutely critical to isolating the cause of slow responses due to FM.  Don't give up on it.  See Carl's later post.
>
> It is not uncommon for FM >6 to run slower than FM6 in specific circumstances.
>
> --steve
>
>
> On 6/20/12 at 3:01 PM, [hidden email] (Patrick Larkin) pronounced:
>
>> Unless you are telling me to put the Filemaker Server IP as the "mydomain" in your example?
>>
>> In that case, I get the source of a 401 Forbidden page.
>>
>>
>> Patrick
>> On Jun 20, 2012, at 2:52 PM, Patrick Larkin wrote:
>>
>>> I just get
>>> /fmi/xml/FMPXMLRESULT.xml?-db= .... (and all the search criteria) in one box and
>> the source of my 404 error page in the other box.
>>>
>>>
>>> Patrick Larkin
>>> Developer/Administrator of Special Systems / Webmaster
>>> Bethlehem Area School District
>>>
>>>
>>>
>>>
>>> On Jun 20, 2012, at 2:19 PM, Carl Ketterling wrote:
>>>
>>>> The first thing I would do is look for the amount of data that's being
>>>> returned.  Steve Piercy gave this information to me in the past:
>>>>
>>>>>  [
>>>>>  inline(...);
>>>>>      $fmresults = include_url('http://mydomain/'+action_statement);
>>>>>  ]
>>>>>  <textarea>[action_statement]</textarea>
>>>>>  <textarea>[$fmresults]</textarea>
>>>>>  [
>>>>>  /inline;
>>>>>  ]
>>>>  In some layouts, I was shocked to see the amount of data being returned.
>>>>  Carl
>>>>    In response to this text from Patrick Larkin ([hidden email])
>>>> sent on Wednesday, June 20, 2012 at 2:02 PM (-0400):
>>>>
>>>>> Hello -
>>>>>  I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>>>>> I'm working on loads significantly faster with Filemaker 6(!) and am
>>>>> trying to track down what the issue might be.
>>>>>  The page simply runs one inline to pull student demographics and another
>>>>> inline from another database to pull a dozen other fields.  The inlines
>>>>> put everything into variables which are then displayed in the page using
>>>>> [var:'theVar'] tags.  Nothing at all unusual.
>>>>>  What are some techniques people use?  I tried moving the [abort] tag
>>>>> around but that only gets me so far.
>>>>>   Patrick  #############################################################
>>>>> This message is sent to you because you are subscribed to
>>>>> the mailing list Lasso
>>>>> [hidden email]
>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>> Send administrative queries to  <[hidden email]>
>>>>   #############################################################
>>>> This message is sent to you because you are subscribed to
>>>> the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>> Send administrative queries to  <[hidden email]>
>>>>
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Steve Piercy               Web Site Builder               Soquel, CA
> <[hidden email]>                  <http://www.StevePiercy.com/>
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
>
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

stevepiercy
That's why you get the 401 Forbidden page.

The first code snippet that Carl provided does not provide the
credentials contained in the auth_group tag.

The second code snippet, also from Carl, should provide the
necessary credentials.
http://lasso.2283332.n4.nabble.com/Ways-to-find-cause-for-page-delay-tp4634919p4634932.html

Alternatively, you can wrap the code snippet with your
auth_group tag.

I wonder if you're not getting all the emails in this thread?  I
recall you had troubles before with the list.  Check Nabble.

--steve


On 6/20/12 at 9:47 PM, [hidden email] (Patrick Larkin) pronounced:

>This particular app was one of the earliest I ever built and
>uses the [auth_group] tag so they run the inline as themselves.
>Sent from my iPad
>
>On Jun 20, 2012, at 7:33 PM, Steve Piercy - Web Site Builder
><[hidden email]> wrote:
>
>>Patrick,
>>
>>Did you provide authentication credentials within your inline?
>>
>>This technique is absolutely critical to isolating the cause of slow responses
>due to FM.  Don't give up on it.  See Carl's later post.
>>
>>It is not uncommon for FM >6 to run slower than FM6 in specific circumstances.
>>
>>--steve
>>
>>
>>On 6/20/12 at 3:01 PM, [hidden email] (Patrick Larkin) pronounced:
>>
>>> Unless you are telling me to put the Filemaker Server IP as the "mydomain" in
>your example?
>>>   In that case, I get the source of a 401 Forbidden page.
>>>    Patrick
>>> On Jun 20, 2012, at 2:52 PM, Patrick Larkin wrote:
>>>
>>>> I just get
>>>> /fmi/xml/FMPXMLRESULT.xml?-db= .... (and all the search criteria) in one box
>and
>>> the source of my 404 error page in the other box.
>>>>    Patrick Larkin
>>>> Developer/Administrator of Special Systems / Webmaster
>>>> Bethlehem Area School District
>>>>      On Jun 20, 2012, at 2:19 PM, Carl Ketterling wrote:
>>>>
>>>>> The first thing I would do is look for the amount of data that's being
>>>>> returned.  Steve Piercy gave this information to me in the past:
>>>>>
>>>>>>  [
>>>>>>  inline(...);
>>>>>>      $fmresults = include_url('http://mydomain/'+action_statement);
>>>>>>  ]
>>>>>>  <textarea>[action_statement]</textarea>
>>>>>>  <textarea>[$fmresults]</textarea>
>>>>>>  [
>>>>>>  /inline;
>>>>>>  ]
>>>>>  In some layouts, I was shocked to see the amount of data being returned.
>>>>>  Carl
>>>>>    In response to this text from Patrick Larkin ([hidden email])
>>>>> sent on Wednesday, June 20, 2012 at 2:02 PM (-0400):
>>>>>
>>>>>> Hello -
>>>>>>  I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>>>>>> I'm working on loads significantly faster with Filemaker 6(!) and am
>>>>>> trying to track down what the issue might be.
>>>>>>  The page simply runs one inline to pull student demographics and another
>>>>>> inline from another database to pull a dozen other fields.  The inlines
>>>>>> put everything into variables which are then displayed in the page using
>>>>>> [var:'theVar'] tags.  Nothing at all unusual.
>>>>>>  What are some techniques people use?  I tried moving the [abort] tag
>>>>>> around but that only gets me so far.
>>>>>>   Patrick  #############################################################
>>>>>> This message is sent to you because you are subscribed to
>>>>>> the mailing list Lasso
>>>>>> [hidden email]
>>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>>> Send administrative queries to  <[hidden email]>
>>>>>   #############################################################
>>>>> This message is sent to you because you are subscribed to
>>>>> the mailing list Lasso
>>>>> [hidden email]
>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>> Send administrative queries to  <[hidden email]>
>>>>>
>>>>   #############################################################
>>>> This message is sent to you because you are subscribed to
>>>> the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>> Send administrative queries to  <[hidden email]>
>>>>
>>>   #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>
>>-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>Steve Piercy               Web Site Builder               Soquel, CA
>><[hidden email]>                  <http://www.StevePiercy.com/>
>>
>>#############################################################
>>This message is sent to you because you are subscribed to
>>the mailing list Lasso
>>[hidden email]
>>To unsubscribe, E-mail to: <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>>
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Johan Solve
In reply to this post by Patrick Larkin-2
This is somewhat the same results I got when migrating an ancient FM6
based site to FMS11 (intermediate migration in wait for a complete
rebuild). FM6 on old G4 server hardware performed MUCH faster than
FMS11 on today's hardware.

I had to do some serious cache juggling with cache priming and all to
get decent performance. Layout optimizations didn't help much. It
seems the Lasso FM SA connector burns a lot of time parsing and
preparing the XML result since the raw response is, ehum, less slow.

I suspect FMS11 on Windows/IIS is one factor since the fairly old Mac
dev server performed better than the Windows server used in
production. We are experimenting with using FMS11 with Apache on
Windows mainly to overcome the hard 60 seconds timeout in IIS that
kills nightly maintenance routines. This setup is not supported by FMI
but seems to work fine. Next step is to find out if performance is any
better with that setup.

2012/6/20 Patrick Larkin <[hidden email]>:

> The strange part is that It is roughly 3 times faster on a three server Filemaker 6 setup (web server + Filemaker Unlimited + Filemaker Server 6) with the Filemaker portion running on archaic G4 towers running 10.2.
>
> The new setup is web server _ Filemaker 10 Server Advanced running on a quad-core Xeon Xserve running 10.5.  The databases were converted without modification to the Filemaker 11 platform.  I expected a marked improvement just on horsepower and OS improvements alone!  :)
>
> Patrick Larkin
> Developer/Administrator of Special Systems / Webmaster
> Bethlehem Area School District
>
>
>
>
> On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:
>
>> one way to get a look at what's happening throughout your page is using some simple timers, however, it sounds like your issues are likely with the Filemaker interaction and not within your lasso code.
>>
>> simple timer:
>> get the page start time in milliseconds
>>       local('start' = date_msec);
>> Anywhere you need to know the elapsed time, output this:
>>       (date_msec - #start)+'ms';
>>
>> by comparing the time elapsed from one code block to the next, you can see how long each piece is taking and compare results if you experiment with different layouts or methods of organizing your data and processing it.
>>
>> It sounds like you may be in for some Filemaker hacking though. reviewing each layout to make sure you have layouts that use properly indexed fields, dont have extra fields on the layout that you are not retrieving, etc. If I recall correctly, Filemaker seems to benefit significantly from nested inlines, so you may want to wrap both inlines in an outer inline or just simply nest the second inline inside the first (not inside the records container ;)  ) and test to see if you get performance gains from there.
>>
>> In addition, you may wish to double check the Filemaker server setup to make sure you have allowed enough resources, as the defaults are not necessarily good for web interaction.
>>
>> Tim Taplin
>>
>> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>>
>>> Hello -
>>>
>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page I'm working on loads significantly faster with Filemaker 6(!) and am trying to track down what the issue might be.
>>>
>>> The page simply runs one inline to pull student demographics and another inline from another database to pull a dozen other fields.  The inlines put everything into variables which are then displayed in the page using [var:'theVar'] tags.  Nothing at all unusual.
>>>
>>> What are some techniques people use?  I tried moving the [abort] tag around but that only gets me so far.
>>>
>>>
>>> Patrick
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>>  the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>



--
Mvh
Johan Sölve
____________________________________
Montania System AB
Halmstad   Stockholm
http://www.montania.se

Johan Sölve
Mobil +46 709-51 55 70
[hidden email]

Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
Telefon +46 35-136800 |  Fax +46 35-136801
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Ke Carlton-3
Based on reports, using odbc with FMSA is much faster.

On Thursday, 21 June 2012, Johan Solve <[hidden email]> wrote:

> This is somewhat the same results I got when migrating an ancient FM6
> based site to FMS11 (intermediate migration in wait for a complete
> rebuild). FM6 on old G4 server hardware performed MUCH faster than
> FMS11 on today's hardware.
>
> I had to do some serious cache juggling with cache priming and all to
> get decent performance. Layout optimizations didn't help much. It
> seems the Lasso FM SA connector burns a lot of time parsing and
> preparing the XML result since the raw response is, ehum, less slow.
>
> I suspect FMS11 on Windows/IIS is one factor since the fairly old Mac
> dev server performed better than the Windows server used in
> production. We are experimenting with using FMS11 with Apache on
> Windows mainly to overcome the hard 60 seconds timeout in IIS that
> kills nightly maintenance routines. This setup is not supported by FMI
> but seems to work fine. Next step is to find out if performance is any
> better with that setup.
>
> 2012/6/20 Patrick Larkin <[hidden email]>:
>> The strange part is that It is roughly 3 times faster on a three server
Filemaker 6 setup (web server + Filemaker Unlimited + Filemaker Server 6)
with the Filemaker portion running on archaic G4 towers running 10.2.
>>
>> The new setup is web server _ Filemaker 10 Server Advanced running on a
quad-core Xeon Xserve running 10.5.  The databases were converted without
modification to the Filemaker 11 platform.  I expected a marked improvement
just on horsepower and OS improvements alone!  :)

>>
>> Patrick Larkin
>> Developer/Administrator of Special Systems / Webmaster
>> Bethlehem Area School District
>>
>>
>>
>>
>> On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:
>>
>>> one way to get a look at what's happening throughout your page is using
some simple timers, however, it sounds like your issues are likely with the
Filemaker interaction and not within your lasso code.
>>>
>>> simple timer:
>>> get the page start time in milliseconds
>>>       local('start' = date_msec);
>>> Anywhere you need to know the elapsed time, output this:
>>>       (date_msec - #start)+'ms';
>>>
>>> by comparing the time elapsed from one code block to the next, you can
see how long each piece is taking and compare results if you experiment
with different layouts or methods of organizing your data and processing it.
>>>
>>> It sounds like you may be in for some Filemaker hacking though.
reviewing each layout to make sure you have layouts that use properly
indexed fields, dont have extra fields on the layout that you are not
retrieving, etc. If I recall correctly, Filemaker seems to benefit
significantly from nested inlines, so you may want to wrap both inlines in
an outer inline or just simply nest the second inline inside the first (not
inside the records container ;)  ) and test to see if you get performance
gains from there.
>>>
>>> In addition, you may wish to double check the Filemaker server setup to
make sure you have allowed enough resources, as the defaults are not
necessarily good for web interaction.
>>>
>>> Tim Taplin
>>>
>>> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>>>
>>>> Hello -
>>>>
>>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
I'm working on loads significantly faster with Filemaker 6(!) and am trying
to track down what the issue might be.
>>>>
>>>> The page simply runs one inline to pull student demographics and
another inline from another database to pull a dozen other fields.  The
inlines put everything into variables which are then displayed in the page
using [var:'theVar'] tags.  Nothing at all unusual.
>>>>
>>>> What are some techniques people use?  I tried moving the [abort] tag
around but that only gets me so far.

>>>>
>>>>
>>>> Patrick
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>> the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>> Send administrative queries to  <[hidden email]>
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>>  the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>>  the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <--
> Mvh
> Johan Sölve
> ____________________________________
> Montania System AB
> Halmstad   Stockholm
> http://www.montania.se
>
> Johan Sölve
> Mobil +46 709-51 55 70
> [hidden email]
>
> Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
> Telefon +46 35-136800 |  Fax +46 35-136801
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
>
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Johan Solve
Not confirmed to work with 8.6 afaik.


2012/6/21 Ke Carlton <[hidden email]>:

> Based on reports, using odbc with FMSA is much faster.
>
> On Thursday, 21 June 2012, Johan Solve <[hidden email]> wrote:
>> This is somewhat the same results I got when migrating an ancient FM6
>> based site to FMS11 (intermediate migration in wait for a complete
>> rebuild). FM6 on old G4 server hardware performed MUCH faster than
>> FMS11 on today's hardware.
>>
>> I had to do some serious cache juggling with cache priming and all to
>> get decent performance. Layout optimizations didn't help much. It
>> seems the Lasso FM SA connector burns a lot of time parsing and
>> preparing the XML result since the raw response is, ehum, less slow.
>>
>> I suspect FMS11 on Windows/IIS is one factor since the fairly old Mac
>> dev server performed better than the Windows server used in
>> production. We are experimenting with using FMS11 with Apache on
>> Windows mainly to overcome the hard 60 seconds timeout in IIS that
>> kills nightly maintenance routines. This setup is not supported by FMI
>> but seems to work fine. Next step is to find out if performance is any
>> better with that setup.
>>
>> 2012/6/20 Patrick Larkin <[hidden email]>:
>>> The strange part is that It is roughly 3 times faster on a three server
> Filemaker 6 setup (web server + Filemaker Unlimited + Filemaker Server 6)
> with the Filemaker portion running on archaic G4 towers running 10.2.
>>>
>>> The new setup is web server _ Filemaker 10 Server Advanced running on a
> quad-core Xeon Xserve running 10.5.  The databases were converted without
> modification to the Filemaker 11 platform.  I expected a marked improvement
> just on horsepower and OS improvements alone!  :)
>>>
>>> Patrick Larkin
>>> Developer/Administrator of Special Systems / Webmaster
>>> Bethlehem Area School District
>>>
>>>
>>>
>>>
>>> On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:
>>>
>>>> one way to get a look at what's happening throughout your page is using
> some simple timers, however, it sounds like your issues are likely with the
> Filemaker interaction and not within your lasso code.
>>>>
>>>> simple timer:
>>>> get the page start time in milliseconds
>>>>       local('start' = date_msec);
>>>> Anywhere you need to know the elapsed time, output this:
>>>>       (date_msec - #start)+'ms';
>>>>
>>>> by comparing the time elapsed from one code block to the next, you can
> see how long each piece is taking and compare results if you experiment
> with different layouts or methods of organizing your data and processing it.
>>>>
>>>> It sounds like you may be in for some Filemaker hacking though.
> reviewing each layout to make sure you have layouts that use properly
> indexed fields, dont have extra fields on the layout that you are not
> retrieving, etc. If I recall correctly, Filemaker seems to benefit
> significantly from nested inlines, so you may want to wrap both inlines in
> an outer inline or just simply nest the second inline inside the first (not
> inside the records container ;)  ) and test to see if you get performance
> gains from there.
>>>>
>>>> In addition, you may wish to double check the Filemaker server setup to
> make sure you have allowed enough resources, as the defaults are not
> necessarily good for web interaction.
>>>>
>>>> Tim Taplin
>>>>
>>>> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>>>>
>>>>> Hello -
>>>>>
>>>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
> I'm working on loads significantly faster with Filemaker 6(!) and am trying
> to track down what the issue might be.
>>>>>
>>>>> The page simply runs one inline to pull student demographics and
> another inline from another database to pull a dozen other fields.  The
> inlines put everything into variables which are then displayed in the page
> using [var:'theVar'] tags.  Nothing at all unusual.
>>>>>
>>>>> What are some techniques people use?  I tried moving the [abort] tag
> around but that only gets me so far.
>>>>>
>>>>>
>>>>> Patrick
>>>>> #############################################################
>>>>> This message is sent to you because you are subscribed to
>>>>> the mailing list Lasso
>>>>> [hidden email]
>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>> Send administrative queries to  <[hidden email]>
>>>>
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>>  the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>> Send administrative queries to  <[hidden email]>
>>>>
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>>  the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <--
>> Mvh
>> Johan Sölve
>> ____________________________________
>> Montania System AB
>> Halmstad   Stockholm
>> http://www.montania.se
>>
>> Johan Sölve
>> Mobil +46 709-51 55 70
>> [hidden email]
>>
>> Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
>> Telefon +46 35-136800 |  Fax +46 35-136801
>> #############################################################
>> This message is sent to you because you are subscribed to
>>  the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>



--
Mvh
Johan Sölve
____________________________________
Montania System AB
Halmstad   Stockholm
http://www.montania.se

Johan Sölve
Mobil +46 709-51 55 70
[hidden email]

Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
Telefon +46 35-136800 |  Fax +46 35-136801
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

stevepiercy
Jono provided an anecdotal claim that ODBC is faster than the
Lasso Connector for FMS9 or FMSA on 8.6, but not any
reproducible test results.
http://lasso.2283332.n4.nabble.com/FileMaker-11-0-99-Custom-Web-Publishing-dead-slow-tp4016733p4017063.html

As far as the IIS timeout, you can change that setting.
http://lasso.2283332.n4.nabble.com/Max-Execution-Time-tp3131750p3131751.html

There's also a hack.
http://lasso.2283332.n4.nabble.com/IIS-Time-out-tp3148506p3148509.html

--steve


On 6/21/12 at 11:19 AM, [hidden email] (Johan Solve) pronounced:

>Not confirmed to work with 8.6 afaik.
>
>
>2012/6/21 Ke Carlton <[hidden email]>:
>>Based on reports, using odbc with FMSA is much faster.
>>
>>On Thursday, 21 June 2012, Johan Solve <[hidden email]> wrote:
>>> This is somewhat the same results I got when migrating an ancient FM6
>>> based site to FMS11 (intermediate migration in wait for a complete
>>> rebuild). FM6 on old G4 server hardware performed MUCH faster than
>>> FMS11 on today's hardware.
>>>
>>> I had to do some serious cache juggling with cache priming and all to
>>> get decent performance. Layout optimizations didn't help much. It
>>> seems the Lasso FM SA connector burns a lot of time parsing and
>>> preparing the XML result since the raw response is, ehum, less slow.
>>>
>>> I suspect FMS11 on Windows/IIS is one factor since the fairly old Mac
>>> dev server performed better than the Windows server used in
>>> production. We are experimenting with using FMS11 with Apache on
>>> Windows mainly to overcome the hard 60 seconds timeout in IIS that
>>> kills nightly maintenance routines. This setup is not supported by FMI
>>> but seems to work fine. Next step is to find out if performance is any
>>> better with that setup.
>>>
>>> 2012/6/20 Patrick Larkin <[hidden email]>:
>>>> The strange part is that It is roughly 3 times faster on a three server
>>Filemaker 6 setup (web server + Filemaker Unlimited + Filemaker Server 6)
>>with the Filemaker portion running on archaic G4 towers running 10.2.
>>>>
>>>> The new setup is web server _ Filemaker 10 Server Advanced running on a
>>quad-core Xeon Xserve running 10.5.  The databases were converted without
>>modification to the Filemaker 11 platform.  I expected a marked improvement
>>just on horsepower and OS improvements alone!  :)
>>>>
>>>> Patrick Larkin
>>>> Developer/Administrator of Special Systems / Webmaster
>>>> Bethlehem Area School District
>>>>
>>>>
>>>>
>>>>
>>>> On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:
>>>>
>>>>> one way to get a look at what's happening throughout your page is using
>>some simple timers, however, it sounds like your issues are likely with the
>>Filemaker interaction and not within your lasso code.
>>>>>
>>>>> simple timer:
>>>>> get the page start time in milliseconds
>>>>>       local('start' = date_msec);
>>>>> Anywhere you need to know the elapsed time, output this:
>>>>>       (date_msec - #start)+'ms';
>>>>>
>>>>> by comparing the time elapsed from one code block to the next, you can
>>see how long each piece is taking and compare results if you experiment
>>with different layouts or methods of organizing your data and processing it.
>>>>>
>>>>> It sounds like you may be in for some Filemaker hacking though.
>>reviewing each layout to make sure you have layouts that use properly
>>indexed fields, dont have extra fields on the layout that you are not
>>retrieving, etc. If I recall correctly, Filemaker seems to benefit
>>significantly from nested inlines, so you may want to wrap both inlines in
>>an outer inline or just simply nest the second inline inside the first (not
>>inside the records container ;)  ) and test to see if you get performance
>>gains from there.
>>>>>
>>>>> In addition, you may wish to double check the Filemaker server setup to
>>make sure you have allowed enough resources, as the defaults are not
>>necessarily good for web interaction.
>>>>>
>>>>> Tim Taplin
>>>>>
>>>>> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>>>>>
>>>>>> Hello -
>>>>>>
>>>>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>>I'm working on loads significantly faster with Filemaker 6(!) and am trying
>>to track down what the issue might be.
>>>>>>
>>>>>> The page simply runs one inline to pull student demographics and
>>another inline from another database to pull a dozen other fields.  The
>>inlines put everything into variables which are then displayed in the page
>>using [var:'theVar'] tags.  Nothing at all unusual.
>>>>>>
>>>>>> What are some techniques people use?  I tried moving the [abort] tag
>>around but that only gets me so far.
>>>>>>
>>>>>>
>>>>>> Patrick
>>>>>> #############################################################
>>>>>> This message is sent to you because you are subscribed to
>>>>>> the mailing list Lasso
>>>>>> [hidden email]
>>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>>> Send administrative queries to  <[hidden email]>
>>>>>
>>>>> #############################################################
>>>>> This message is sent to you because you are subscribed to
>>>>>  the mailing list Lasso
>>>>> [hidden email]
>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>> Send administrative queries to  <[hidden email]>
>>>>>
>>>>
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>>  the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <--
>>> Mvh
>>> Johan Sölve
>>> ____________________________________
>>> Montania System AB
>>> Halmstad   Stockholm
>>> http://www.montania.se
>>>
>>> Johan Sölve
>>> Mobil +46 709-51 55 70
>>> [hidden email]
>>>
>>> Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
>>> Telefon +46 35-136800 |  Fax +46 35-136801
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>>  the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>>
>>#############################################################
>>This message is sent to you because you are subscribed to
>> the mailing list Lasso
>>[hidden email]
>>To unsubscribe, E-mail to: <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>
>
>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Patrick Larkin-2
Has anyone actually done ODBC and Lasso on Filemaker Server 10?  

I have Filemaker clients accessing MySQL over ODBC by installing MySQL's provided ODBC driver on the Filemaker Server and then setting up the Filemaker database accordingly.  

This, however, is the opposite.  I want Filemaker to do be the data source but I don't see any ODBC driver from Filemaker to run on the server so Lasso will see it.  I'm assuming I have to install a driver on the Filemaker Server (other than the MySQL driver used for a solely different purpose) and set it up as a DSN using Apple's ODBC Administrator.  THen I need to tell Lasso about it.

But where is this elusive driver?


Patrick

On Jun 21, 2012, at 5:32 AM, Steve Piercy - Web Site Builder wrote:

> Jono provided an anecdotal claim that ODBC is faster than the Lasso Connector for FMS9 or FMSA on 8.6, but not any reproducible test results.
> http://lasso.2283332.n4.nabble.com/FileMaker-11-0-99-Custom-Web-Publishing-dead-slow-tp4016733p4017063.html
>
> As far as the IIS timeout, you can change that setting.
> http://lasso.2283332.n4.nabble.com/Max-Execution-Time-tp3131750p3131751.html
>
> There's also a hack.
> http://lasso.2283332.n4.nabble.com/IIS-Time-out-tp3148506p3148509.html
>
> --steve
>
>
> On 6/21/12 at 11:19 AM, [hidden email] (Johan Solve) pronounced:
>
>> Not confirmed to work with 8.6 afaik.
>>
>>
>> 2012/6/21 Ke Carlton <[hidden email]>:
>>> Based on reports, using odbc with FMSA is much faster.
>>>
>>> On Thursday, 21 June 2012, Johan Solve <[hidden email]> wrote:
>>>> This is somewhat the same results I got when migrating an ancient FM6
>>>> based site to FMS11 (intermediate migration in wait for a complete
>>>> rebuild). FM6 on old G4 server hardware performed MUCH faster than
>>>> FMS11 on today's hardware.
>>>>
>>>> I had to do some serious cache juggling with cache priming and all to
>>>> get decent performance. Layout optimizations didn't help much. It
>>>> seems the Lasso FM SA connector burns a lot of time parsing and
>>>> preparing the XML result since the raw response is, ehum, less slow.
>>>>
>>>> I suspect FMS11 on Windows/IIS is one factor since the fairly old Mac
>>>> dev server performed better than the Windows server used in
>>>> production. We are experimenting with using FMS11 with Apache on
>>>> Windows mainly to overcome the hard 60 seconds timeout in IIS that
>>>> kills nightly maintenance routines. This setup is not supported by FMI
>>>> but seems to work fine. Next step is to find out if performance is any
>>>> better with that setup.
>>>>
>>>> 2012/6/20 Patrick Larkin <[hidden email]>:
>>>>> The strange part is that It is roughly 3 times faster on a three server
>>> Filemaker 6 setup (web server + Filemaker Unlimited + Filemaker Server 6)
>>> with the Filemaker portion running on archaic G4 towers running 10.2.
>>>>>
>>>>> The new setup is web server _ Filemaker 10 Server Advanced running on a
>>> quad-core Xeon Xserve running 10.5.  The databases were converted without
>>> modification to the Filemaker 11 platform.  I expected a marked improvement
>>> just on horsepower and OS improvements alone!  :)
>>>>>
>>>>> Patrick Larkin
>>>>> Developer/Administrator of Special Systems / Webmaster
>>>>> Bethlehem Area School District
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Jun 20, 2012, at 3:36 PM, Tim Taplin wrote:
>>>>>
>>>>>> one way to get a look at what's happening throughout your page is using
>>> some simple timers, however, it sounds like your issues are likely with the
>>> Filemaker interaction and not within your lasso code.
>>>>>>
>>>>>> simple timer:
>>>>>> get the page start time in milliseconds
>>>>>>       local('start' = date_msec);
>>>>>> Anywhere you need to know the elapsed time, output this:
>>>>>>       (date_msec - #start)+'ms';
>>>>>>
>>>>>> by comparing the time elapsed from one code block to the next, you can
>>> see how long each piece is taking and compare results if you experiment
>>> with different layouts or methods of organizing your data and processing it.
>>>>>>
>>>>>> It sounds like you may be in for some Filemaker hacking though.
>>> reviewing each layout to make sure you have layouts that use properly
>>> indexed fields, dont have extra fields on the layout that you are not
>>> retrieving, etc. If I recall correctly, Filemaker seems to benefit
>>> significantly from nested inlines, so you may want to wrap both inlines in
>>> an outer inline or just simply nest the second inline inside the first (not
>>> inside the records container ;)  ) and test to see if you get performance
>>> gains from there.
>>>>>>
>>>>>> In addition, you may wish to double check the Filemaker server setup to
>>> make sure you have allowed enough resources, as the defaults are not
>>> necessarily good for web interaction.
>>>>>>
>>>>>> Tim Taplin
>>>>>>
>>>>>> On Jun 20, 2012, at 12:02 PM, Patrick Larkin wrote:
>>>>>>
>>>>>>> Hello -
>>>>>>>
>>>>>>> I'm trying out some things with Lasso 8.6 and Filemaker 11.  The page
>>> I'm working on loads significantly faster with Filemaker 6(!) and am trying
>>> to track down what the issue might be.
>>>>>>>
>>>>>>> The page simply runs one inline to pull student demographics and
>>> another inline from another database to pull a dozen other fields.  The
>>> inlines put everything into variables which are then displayed in the page
>>> using [var:'theVar'] tags.  Nothing at all unusual.
>>>>>>>
>>>>>>> What are some techniques people use?  I tried moving the [abort] tag
>>> around but that only gets me so far.
>>>>>>>
>>>>>>>
>>>>>>> Patrick
>>>>>>> #############################################################
>>>>>>> This message is sent to you because you are subscribed to
>>>>>>> the mailing list Lasso
>>>>>>> [hidden email]
>>>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>>>> Send administrative queries to  <[hidden email]>
>>>>>>
>>>>>> #############################################################
>>>>>> This message is sent to you because you are subscribed to
>>>>>>  the mailing list Lasso
>>>>>> [hidden email]
>>>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>>>> Send administrative queries to  <[hidden email]>
>>>>>>
>>>>>
>>>>> #############################################################
>>>>> This message is sent to you because you are subscribed to
>>>>>  the mailing list Lasso
>>>>> [hidden email]
>>>>> To unsubscribe, E-mail to: <--
>>>> Mvh
>>>> Johan Sölve
>>>> ____________________________________
>>>> Montania System AB
>>>> Halmstad   Stockholm
>>>> http://www.montania.se
>>>>
>>>> Johan Sölve
>>>> Mobil +46 709-51 55 70
>>>> [hidden email]
>>>>
>>>> Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
>>>> Telefon +46 35-136800 |  Fax +46 35-136801
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>>  the mailing list Lasso
>>>> [hidden email]
>>>> To unsubscribe, E-mail to: <[hidden email]>
>>>> Send administrative queries to  <[hidden email]>
>>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>>  the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>
>>
>>
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Steve Piercy               Web Site Builder               Soquel, CA
> <[hidden email]>                  <http://www.StevePiercy.com/>
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Ways to find cause for page delay

Patrick Larkin-2
In reply to this post by Tim Taplin
No named inlines.  

The result of these particular inlines can only ever have one result.  So there is no iteration or looping or anything.  Look up a student, display their stuff.  


Patrick


On Jun 20, 2012, at 4:32 PM, Tim Taplin wrote:

> Are you using named inlines? or are you grabbing the data and setting to a var that you iterate thru?
>
> If you are using the named inlines then the main overhead doesnt happen until you call it, the query is just saved until you call for the request.
>
> May be worth putting timer inside the inline before the records loop(if you are not using named inlines) and then in each iteration of the inline records, just to get a better feel whether there's something happening in each iteration that's causing the heavy load time.
>
> Tim Taplin

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
12