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 tothe mailing list
|
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 tothe mailing list
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...