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 = 112749
interpreted = N
texte = 332 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 . 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)
332 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 . Kenneth Grome

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:

[ot] RH 7.2 WU-FTP Question (2003) Grep Ampersands (2008) WebCat editing, SiteGuard & SiteEdit (1997) Price and Formula.db (2002) WebCat B13 Mac CGI -- Frames question (1997) WebCat2 - [format thousands] (1997) WebCatalog2 Feature Feedback (1996) [ShowIf] if the varieable exists (1998) MATH TIME (1997) Limiting user access to .tmpl files (1997) F3 crashing server (1997) Frames and WebCat (1997) required fields (1998) [OT] Favourite Firefox Extensions (2004) default value from Lookup (was Grant, please help me) (1997) [/application] error? (1997) shownext not showing next...still r2 (1997) PCS Frames (1997) Setting up WebCatalog with Retail Pro data (1996) WebCatalog can't find database (1997)