Re: [WebDNA] max number of searches and lookups on a page

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 112750
interpreted = N
texte = 333 --047d7b343ef47456990531b3e886 Content-Type: text/plain; charset=UTF-8 Thanks for the tips Ken. All works quite well as is (at least locally on my desktop server) but all those searches and lookups I have do seem clunky. I'm reworking stuff to go with bunches of text variables from just a few searchs. On Sat, Apr 30, 2016 at 8:36 AM, Kenneth Grome wrote: > Grant 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. And it's not possible to use lookups when the > 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. 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. This allows me to start and end > my search without nesting any other contexts inside. 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. 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. > > > > 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 . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --047d7b343ef47456990531b3e886 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks for the tips Ken.

All works quit= e well as is (at least locally on my desktop server) but all those searches= and lookups I have do seem clunky.=C2=A0

I'm = reworking stuff to go with bunches of text variables from just a few search= s.


On Sat, Apr 30, 2016 at 8:36 AM, Kenneth Grome <ken@webd= nasolutions.com> wrote:
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

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --047d7b343ef47456990531b3e886-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] max number of searches and lookups on a page (Kenneth Grome 2016)
  2. Re: [WebDNA] max number of searches and lookups on a page ("Matthew A Perosi, Psi Prime" 2016)
  3. Re: [WebDNA] max number of searches and lookups on a page (Richard Kwasniewski 2016)
  4. Re: [WebDNA] max number of searches and lookups on a page (Kenneth Grome 2016)
  5. [WebDNA] max number of searches and lookups on a page (Richard Kwasniewski 2016)
333 --047d7b343ef47456990531b3e886 Content-Type: text/plain; charset=UTF-8 Thanks for the tips Ken. All works quite well as is (at least locally on my desktop server) but all those searches and lookups I have do seem clunky. I'm reworking stuff to go with bunches of text variables from just a few searchs. On Sat, Apr 30, 2016 at 8:36 AM, Kenneth Grome wrote: > Grant 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. And it's not possible to use lookups when the > 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. 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. This allows me to start and end > my search without nesting any other contexts inside. 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. 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. > > > > 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 . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --047d7b343ef47456990531b3e886 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks for the tips Ken.

All works quit= e well as is (at least locally on my desktop server) but all those searches= and lookups I have do seem clunky.=C2=A0

I'm = reworking stuff to go with bunches of text variables from just a few search= s.


On Sat, Apr 30, 2016 at 8:36 AM, Kenneth Grome <ken@webd= nasolutions.com> wrote:
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

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --047d7b343ef47456990531b3e886-- . Richard Kwasniewski

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

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...

Related Readings:

WebCat2 - storing unformatted date data? (1997) upgrading (1997) Mac Webcat 3.0.3b1 memory leak redirect inside search (1998) WebCat2: multiple currency support (1997) [OT] HTML TAB CODE (2002) [WebDNA] Grep out square brackets? (2010) Fufillment e-mail? (1998) WebCat b15 Mac plug-in (1997) [input] questions (1997) WebCat2 - Getting to the browser's username/password data (1997) webdelivery not working (1998) The Best Shopping Cart Solution I Have Come Upon (2003) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) emailer (1997) Text data with spaces in them... (1997) sandboxes with 6.0 (2004) [SHOWIF] (1997) Re:no [search] with NT (1997) Just Testing (1997) Changing RAM-cached browser values ... (2000)