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 = 112751
interpreted = N
texte = 334 This is a multi-part message in MIME format. --------------1973AB8AE9DA5B7BF70C9BEF Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hey Ken, I'd like a confirmation on the "thousands" of text variables you set on a page. I hit a hard limit of text variables many years ago, I think it was about 255. Since then I've been writing scripts to avoid that hard limit. Anyone know the max number of text variables and math variable that can be active for a single script? -Matt Perosi On 4/30/2016 9: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 > > -- Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator matt@psiprime.com Psi Prime 323 Union Blvd. Totowa, NJ 07512 Direct: 888.872.0274 Fax: 888.488.5924 http://www.perosi.com --------------1973AB8AE9DA5B7BF70C9BEF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable


Hey Ken,

I'd like a confirmation on the "thousands" of text variables you set on a page.=C2=A0 I hit a hard limit of text variables many years ago,= I think it was about 255.=C2=A0 Since then I've been writing scripts to avoid that hard limit.

Anyone know the max number of text variables and math variable that can be active for a single script?

-Matt Perosi


On 4/30/2016 9:36 AM, Kenneth Grome wrote:
Grant once told me that doing three lookups takes ab=out the sameamount of resources as a single search ... so if you're doingthree or more lookups in a single db record you're actually betteroff replacing them with a single search.I seldom use lookups because I typically need data from more thanone field anyways.  And it's not possible to use lookups when thevalue you're seeking might not be an exact (case sensitive) match,so this is another limitation of lookups that encourage me to usesearches more often.I avoid nested contexts as much as possible too, because the morenesting you employ the more resources are used.  Sometimes thingscan get pretty slow when nesting too much ... :(I generally prefer to avoid nesting by putting my search contextsat the top of the page, then setting the values I need from thefounditems context as text vars.  This allows me to start and endmy search without nesting any other contexts inside.  Then when Iactually need the db values from the founditems context further ondown the page, they are all available as text variables.I use text variables extensively and have never had a problemsetting hundreds or even thousands on a page.  I think the use oftext variables to avoid nested contexts, and using searches toavoid multiple lookups, makes good sense.Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server AdministrationOn 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 ofboth so I'm slimming things down with text variables. Seems clunkythe way I have it setup now.Currently there 14 searches and 57 lookups or so. I can slim thatdown to 7 searches, probably no fewer than that, the number oflookups I'm just starting to slim down....=20I believe the docs also said the number of text variables isdependent 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 oncethen all those text variables in ram start to add up? That beingthe case am I better off having more searches and/or lookups thangoing the text variable route.
----------------------------------------------------=-----This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us

--=20Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & Educatorm=att@psiprime.comPsi Prime323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://=www.perosi.com
--------------------------------------------------------- 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 --------------1973AB8AE9DA5B7BF70C9BEF-- . 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)
334 This is a multi-part message in MIME format. --------------1973AB8AE9DA5B7BF70C9BEF Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hey Ken, I'd like a confirmation on the "thousands" of text variables you set on a page. I hit a hard limit of text variables many years ago, I think it was about 255. Since then I've been writing scripts to avoid that hard limit. Anyone know the max number of text variables and math variable that can be active for a single script? -Matt Perosi On 4/30/2016 9: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 > > -- Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator matt@psiprime.com Psi Prime 323 Union Blvd. Totowa, NJ 07512 Direct: 888.872.0274 Fax: 888.488.5924 http://www.perosi.com --------------1973AB8AE9DA5B7BF70C9BEF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable


Hey Ken,

I'd like a confirmation on the "thousands" of text variables you set on a page.=C2=A0 I hit a hard limit of text variables many years ago,= I think it was about 255.=C2=A0 Since then I've been writing scripts to avoid that hard limit.

Anyone know the max number of text variables and math variable that can be active for a single script?

-Matt Perosi


On 4/30/2016 9:36 AM, Kenneth Grome wrote:
Grant once told me that doing three lookups takes ab=out the sameamount of resources as a single search ... so if you're doingthree or more lookups in a single db record you're actually betteroff replacing them with a single search.I seldom use lookups because I typically need data from more thanone field anyways.  And it's not possible to use lookups when thevalue you're seeking might not be an exact (case sensitive) match,so this is another limitation of lookups that encourage me to usesearches more often.I avoid nested contexts as much as possible too, because the morenesting you employ the more resources are used.  Sometimes thingscan get pretty slow when nesting too much ... :(I generally prefer to avoid nesting by putting my search contextsat the top of the page, then setting the values I need from thefounditems context as text vars.  This allows me to start and endmy search without nesting any other contexts inside.  Then when Iactually need the db values from the founditems context further ondown the page, they are all available as text variables.I use text variables extensively and have never had a problemsetting hundreds or even thousands on a page.  I think the use oftext variables to avoid nested contexts, and using searches toavoid multiple lookups, makes good sense.Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server AdministrationOn 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 ofboth so I'm slimming things down with text variables. Seems clunkythe way I have it setup now.Currently there 14 searches and 57 lookups or so. I can slim thatdown to 7 searches, probably no fewer than that, the number oflookups I'm just starting to slim down....=20I believe the docs also said the number of text variables isdependent 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 oncethen all those text variables in ram start to add up? That beingthe case am I better off having more searches and/or lookups thangoing the text variable route.
----------------------------------------------------=-----This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us

--=20Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & Educatorm=att@psiprime.comPsi Prime323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://=www.perosi.com
--------------------------------------------------------- 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 --------------1973AB8AE9DA5B7BF70C9BEF-- . "Matthew A Perosi, Psi Prime"

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:

RE: Automatic thumbnail images (1998) [math] with first letter in field? (1997) target=_blank and form variables (1997) Banner DNA (1997) Opinion: [input] should be called [output] ... (1997) can webcat create directories on NT? (1997) 2nd try: possible to weight results of grouped fieldssearch? (1998) Everyone: List Traffic (was [include ...] behavior) (1997) Show shoppingcart after remove last item (1997) Tech support (2000) Include a big block of text (1997) Email Newsletters (2003) serial number dishing (1997) Hide Ifs (2000) [taxrate] question (1997) [searchString] (1997) Encrypted items in DB (2001) WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997) [WebDNA] Successful, working WebDNA7/CentOS install? (2013) Giving out error pages (1997)