Optimizing [founditems]
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 27116
interpreted = N
texte = Just curious: I state, a search can be considered as active until [/search]. So we should keep the code within the search context as short as possible.Most responsibe for speed is: 1 - The amount of code in the whole template (loading time). 2 - The type of search (complex or not). 3 - The amount and complexity of code within [founditems]. 4 - Available RAM, number and size of loaded databases. Example 1 Single [founditems] and many, many stuff depending on a two-state variable: --------------------------------------- [search...] [founditems] [showif [MyVariable]=on] ...many difficult things to do... [/showif] [showif [MyVariable]=off] ...many difficult things to do... [/showif] [/founditems] [/search] --------------------------------------- I do this most times and (shame) I believe it is the worst method. we have to load one huge page first, then validate all showif's within [founditems]. And showif's can get much more complex than in the example! Example 2 Two [founditems] and many, many stuff depending on a two-state variable: --------------------------------------- [search...] [showif [MyVariable]=on] [founditems] ...many difficult things to do... [/founditems] [/showif] [showif [MyVariable]=off] [founditems] ...many difficult things to do... [/founditems] [/showif] [/search] --------------------------------------- Overall code is equal, but less to do within [founditems]. Might fit better for medium size. I think about adopting this method for all rather short standard searches. Nonsense? Just theory? Example 3 One [founditems] and different include's depending on a multi-state variable: --------------------------------------- [search...] [founditems] [include result_[MyVariable].inc] [/founditems] [/search] --------------------------------------- 5 Lines only and loading just what needed. It requires more templates, but is still maintainable. Now my question: Does example 3 give us most possible speed, or might we loose performance while loading files from disk? Peter ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to
.This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
| |
- Optimizing [founditems] (Peter Ostry 2000)
|
Just curious: I state, a search can be considered as active until [/search]. So we should keep the code within the search context as short as possible.Most responsibe for speed is: 1 - The amount of code in the whole template (loading time). 2 - The type of search (complex or not). 3 - The amount and complexity of code within [founditems]. 4 - Available RAM, number and size of loaded databases. Example 1 Single [founditems] and many, many stuff depending on a two-state variable: --------------------------------------- [search...] [founditems] [showif [MyVariable]=on] ...many difficult things to do... [/showif] [showif [MyVariable]=off] ...many difficult things to do... [/showif] [/founditems] [/search] --------------------------------------- I do this most times and (shame) I believe it is the worst method. we have to load one huge page first, then validate all showif's within [founditems]. And showif's can get much more complex than in the example! Example 2 Two [founditems] and many, many stuff depending on a two-state variable: --------------------------------------- [search...] [showif [MyVariable]=on] [founditems] ...many difficult things to do... [/founditems] [/showif] [showif [MyVariable]=off] [founditems] ...many difficult things to do... [/founditems] [/showif] [/search] --------------------------------------- Overall code is equal, but less to do within [founditems]. Might fit better for medium size. I think about adopting this method for all rather short standard searches. Nonsense? Just theory? Example 3 One [founditems] and different include's depending on a multi-state variable: --------------------------------------- [search...] [founditems] [include result_[MyVariable].inc] [/founditems] [/search] --------------------------------------- 5 Lines only and loading just what needed. It requires more templates, but is still maintainable. Now my question: Does example 3 give us most possible speed, or might we loose performance while loading files from disk? Peter ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Peter Ostry
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:
Locking up with WebCatalog... (1997)
Requiring that certain fields be completed (1997)
formatting a number (1999)
more trouble with [showif] in [search] = busted [shownext] (2000)
[WebDNA] sendmail html with image attachments (2008)
Reversed words (1997)
Location of Browser Info.txt file (1997)
Summary layout (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
Trouble with formula.db (1997)
Getting total number of items ordered (1997)
PCS Frames (1997)
HELP WITH DATES (1997)
The future of WebCatalog is coming with 4.0... (2000)
Protect (1997)
[group] ? (1997)
Date math (1997)
A little syntax help (1997)
weird happenings (1997)
Information on Vieworders.tpl (1998)