Gra=nt once told me that doing three lookups takes about the same
amount of resources as a single search ... so if you're doing
three or more lookups in a single db record you're actually better
off replacing them with a single search.
I seldom use lookups because I typically need data from more than
one field anyways.=C2=A0 And it's not possible to use lookups when the<=br>value you're seeking might not be an exact (case sensitive) match,
so this is another limitation of lookups that encourage me to use
searches more often.
I avoid nested contexts as much as possible too, because the more
nesting you employ the more resources are used.=C2=A0 Sometimes things
can get pretty slow when nesting too much ... :(
I generally prefer to avoid nesting by putting my search contexts
at the top of the page, then setting the values I need from the
founditems context as text vars.=C2=A0 This allows me to start and end
my search without nesting any other contexts inside.=C2=A0 Then when I
actually need the db values from the founditems context further on
down the page, they are all available as text variables.
I use text variables extensively and have never had a problem
setting hundreds or even thousands on a page.=C2=A0 I think the use of
text variables to avoid nested contexts, and using searches to
avoid multiple lookups, makes good sense.
Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Administration---------------------------------------------------------
On 04/30/2016 07:40 AM, Richard Kwasniewski wrote:
> Just curious.
>
> Whats the most lookups and/or searches you've even had on a page.<=br>>
> I have a page being worked on that seems to have way tooo many of
> both so I'm slimming things down with text variables. Seems clunky=
> the way I have it setup now.
>
> Currently there 14 searches and 57 lookups or so. I can slim that
> down to 7 searches, probably no fewer than that, the number of
> lookups I'm just starting to slim down....
>
> I believe the docs also said the number of text variables is
> dependent on available ram.
>
> Is it bad to have a whole of text variables on a page?
>
> I'm guessing if this one page is accessed by many people at once> then all those text variables in ram start to add up? That being
> the case am I better off having more searches and/or lookups than
> going the text variable route.
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
|
Gra=nt once told me that doing three lookups takes about the same
amount of resources as a single search ... so if you're doing
three or more lookups in a single db record you're actually better
off replacing them with a single search.
I seldom use lookups because I typically need data from more than
one field anyways.=C2=A0 And it's not possible to use lookups when the<=br>value you're seeking might not be an exact (case sensitive) match,
so this is another limitation of lookups that encourage me to use
searches more often.
I avoid nested contexts as much as possible too, because the more
nesting you employ the more resources are used.=C2=A0 Sometimes things
can get pretty slow when nesting too much ... :(
I generally prefer to avoid nesting by putting my search contexts
at the top of the page, then setting the values I need from the
founditems context as text vars.=C2=A0 This allows me to start and end
my search without nesting any other contexts inside.=C2=A0 Then when I
actually need the db values from the founditems context further on
down the page, they are all available as text variables.
I use text variables extensively and have never had a problem
setting hundreds or even thousands on a page.=C2=A0 I think the use of
text variables to avoid nested contexts, and using searches to
avoid multiple lookups, makes good sense.
Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Administration---------------------------------------------------------
On 04/30/2016 07:40 AM, Richard Kwasniewski wrote:
> Just curious.
>
> Whats the most lookups and/or searches you've even had on a page.<=br>>
> I have a page being worked on that seems to have way tooo many of
> both so I'm slimming things down with text variables. Seems clunky=
> the way I have it setup now.
>
> Currently there 14 searches and 57 lookups or so. I can slim that
> down to 7 searches, probably no fewer than that, the number of
> lookups I'm just starting to slim down....
>
> I believe the docs also said the number of text variables is
> dependent on available ram.
>
> Is it bad to have a whole of text variables on a page?
>
> I'm guessing if this one page is accessed by many people at once> then all those text variables in ram start to add up? That being
> the case am I better off having more searches and/or lookups than
> going the text variable route.
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...