Re: Summary search -- speed

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 12128
interpreted = N
texte = The summary search could cause you some speed concerns, but not just due to a large number of records. The only speed hit would occur if the number of unique values (size of the summary list) became very large (that is, increased at the same rate as the number of records). If the number of unique values stays roughly the same as the number of records increases, there shouldn't be any unecessary speed concerns. I hope this helps.John.>The summary search command appears very useful for pulling out unique fields, >such as the categories in the Tea Room example that ships with 2.0. > >I'm wondering what type of speed this summary search command has over large >databases. If the inventory was in the 100K records range, would there be a >significant speed hit for a unique entry summary search? Would I be better off >with a separate data table that kept a unique list of categories, etc? > >I don't yet have the large inventory database to play with, but I need to plan >ahead for it. > >Thanks > >Sandy John A. Hill Pacific Coast Software 11770 Bernardo Plaza Ct. #453 * Web tools for Macintosh and WinNT * San Diego, CA 92128 http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: Summary search -- speed (Sandra L. Pitner <76501.3521@CompuServe.COM> 1997)
  2. Re: Summary search -- speed (Grant Hulbert 1997)
  3. Re: Summary search -- speed (Sandra L. Pitner <76501.3521@CompuServe.COM> 1997)
  4. Re: Summary search -- speed (Kenneth Grome 1997)
  5. Re: Summary search -- speed (Kenneth Grome 1997)
  6. Re: Summary search -- speed (John Hill 1997)
  7. Re: Summary search -- speed (Sandra L. Pitner <76501.3521@CompuServe.COM> 1997)
  8. Re: Summary search -- speed (John Hill 1997)
  9. Re: Summary search -- speed (Sandra L. Pitner <76501.3521@CompuServe.COM> 1997)
The summary search could cause you some speed concerns, but not just due to a large number of records. The only speed hit would occur if the number of unique values (size of the summary list) became very large (that is, increased at the same rate as the number of records). If the number of unique values stays roughly the same as the number of records increases, there shouldn't be any unecessary speed concerns. I hope this helps.John.>The summary search command appears very useful for pulling out unique fields, >such as the categories in the Tea Room example that ships with 2.0. > >I'm wondering what type of speed this summary search command has over large >databases. If the inventory was in the 100K records range, would there be a >significant speed hit for a unique entry summary search? Would I be better off >with a separate data table that kept a unique list of categories, etc? > >I don't yet have the large inventory database to play with, but I need to plan >ahead for it. > >Thanks > >Sandy John A. Hill Pacific Coast Software 11770 Bernardo Plaza Ct. #453 * Web tools for Macintosh and WinNT * San Diego, CA 92128 http://www.smithmicro.com John Hill

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:

Reversed words (1997) Summing fields (1997) [URL] around a [sendmail] recipient? (2000) Applescript, WebDNA, and PDF (1997) PC Authorize & Webmerchant (1998) [Semi-OT] ImageMagick Path Weirdness (2005) Re:Copyright ? (1997) default error on NT? (1997) [shownext] and sort (1998) [defined]ish (1997) Price Not Appearing (2000) Superfilous Characters (1998) Triggers and coupons (two questions) (2003) Search for dates greater than [date] (1997) WebObjects (2000) Header info in content (1998) Mac 2.1b2 speed (1997) PC site chck pls (2003) [COMMITDATABASE FileName] (2000) [WebDNA] Version 7.x: webdna.ini and EmailerPrefs (2012)