Re: [WebDNA] Server load

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 100584
interpreted = N
texte = First a belated thank you to all who contributed to this thread earlier this month. I was unable to participate much myself at that time but there was lots and lots of useful information how to make a site leaner and meaner (and faster). Maybe there ought to be an article on this at the WebDNA site? One follow up question: I have this rather big database and need to retrieve three fields from the same entry to place in different places on a web page with lots of static content between the three. There are five ways to do this. Which one is recommended? 1) Merge the three fields with all the static content in between added to each and every entry. + Only a single [LOOKUP] is needed. - Increases the database size considerably. - Increases the amount of data retrieved from the database rather than being included in the template. 2) Merge the three fields with [INCLUDE] commands for the static content. + Only a single [LOOKUP] is needed. + Database not much larger than with three separate fields. - Is it really that much better to collect data from text files with [INCLUDE] than from a database? 3) Do a single [SEARCH] at the beginning and store the data as variables. + One fairly simple and compact search context. - Lots of data stored as variables. - The [SEARCH] command still goes through the entire database even though only one clearly identifiable entry is needed. 4) Incorporate the entire page in a [SEARCH] context + needs just one [SEARCH] command. - Still requires a full search through an oversized database. - Coding is considerably messier than option 2. 5) Use three separate [LOOKUP] commands + By far the simplest solution ? A [LOOKUP] is faster than a [SEARCH] but is it so much faster that *three* of them are better than a single search? Frank Nordberg http://www.musicaviva.com http://stores.ebay.com/Nordbergs-Music-Store?refid=store http://www.abc-notation.com http://www.online-guitarist.com http://www.gitar-siden.com http://www.tablatvre.com http://www.mandolin-player.com http://www.blues-harmonica.com http://www.irish-banjo.com http://www.blues-banjo.com http://www.folk-banjo.com http://www.roarogfrank.com Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Server load (Frank Nordberg 2008)
  2. Re: [WebDNA] Server load (Paul Willis 2008)
  3. Re: [WebDNA] Server load ("Brian B. Burton" 2008)
  4. Re: [WebDNA] Server load (Frank Nordberg 2008)
  5. Re: [WebDNA] Server load (Terry Wilson 2008)
  6. Re: [WebDNA] Server load (Patrick Junkroski 2008)
  7. Re: [WebDNA] Server load (Frank Nordberg 2008)
  8. Re: [WebDNA] Server load ("Brian B. Burton" 2008)
  9. [WebDNA] Server load (Frank Nordberg 2008)
First a belated thank you to all who contributed to this thread earlier this month. I was unable to participate much myself at that time but there was lots and lots of useful information how to make a site leaner and meaner (and faster). Maybe there ought to be an article on this at the WebDNA site? One follow up question: I have this rather big database and need to retrieve three fields from the same entry to place in different places on a web page with lots of static content between the three. There are five ways to do this. Which one is recommended? 1) Merge the three fields with all the static content in between added to each and every entry. + Only a single [lookup] is needed. - Increases the database size considerably. - Increases the amount of data retrieved from the database rather than being included in the template. 2) Merge the three fields with [include] commands for the static content. + Only a single [lookup] is needed. + Database not much larger than with three separate fields. - Is it really that much better to collect data from text files with [include] than from a database? 3) Do a single [search] at the beginning and store the data as variables. + One fairly simple and compact search context. - Lots of data stored as variables. - The [search] command still goes through the entire database even though only one clearly identifiable entry is needed. 4) Incorporate the entire page in a [search] context + needs just one [search] command. - Still requires a full search through an oversized database. - Coding is considerably messier than option 2. 5) Use three separate [lookup] commands + By far the simplest solution ? A [lookup] is faster than a [search] but is it so much faster that *three* of them are better than a single search? Frank Nordberg http://www.musicaviva.com http://stores.ebay.com/Nordbergs-Music-Store?refid=store http://www.abc-notation.com http://www.online-guitarist.com http://www.gitar-siden.com http://www.tablatvre.com http://www.mandolin-player.com http://www.blues-harmonica.com http://www.irish-banjo.com http://www.blues-banjo.com http://www.folk-banjo.com http://www.roarogfrank.com Frank Nordberg

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:

separate by mont (search) (2002) [WebDNA] Sandbox Triggers (2008) shipCost not working v2.1b4 (1997) [Announce]: Web server security and password protection (1997) Re: (1997) Country & Ship-to address & other fields ? (1997) Resume Catalog ? (1997) Reversed words (1997) [WebDNA] naming math vars in v.7 (2010) Cancel Subscription (1996) Assigning Serialized Customer Numbers (1997) problems with WebCat-Plugin (1997) WebCat2b12 CGI Mac - [shownext] problem (1997) Storefornts (1997) server side includes & webcatalog (2000) Email Format (1998) NT error logs (1997) FW: Username and password in tcp connect/send (2001) Searching multiple fields from one form field (1997) [DOS] (1999)