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:
Shopping cart now bad (1997)
Mac Scheduling (1998)
My solution... (1996)
Opinion: [input] should be called [output] ... (1997)
Changes to the List (1997)
2.0Beta Command Ref (can't find this instruction) (1997)
ShowNext (1997)
Searching blank fields problem (1999)
[SMSI]Price and Formula.db (2002)
SMSI BUG: RandSeed broken on 4.0.2 / Mac OS X (2002)
General WebCatalog Questions (1997)
Memory Error message (1998)
Obtaining a dice result (2007)
Displaying text and populating form fields (2005)
Problems with Price field (1997)
Security Hole (1998)
XML Parse with XML WebDNA Syntax... (2004)
setlineiems and UnitShip Cost (2000)
[WebDNA] Crashing again (2008)
Separate SSL Server (1997)