Re: Summary search -- speed

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 12158
interpreted = N
texte = >Just to make sure I understand correctly, you are saying that if I have about 10 >-20 unique categories, the speed is the same whether or not I have 100, 1000 or >100,000 records? > >Slowness occurs when the # of unique categories increases drastically from 10-20 >to 100's or more?Actually it slows down (as you'd expect) the more items in the database. WebCatalog has to search thru all 100,000 records to find the items to summarize, so naturally it would be faster if there were only 1,000 records to look thru. I think John was saying that there's an extra slowdown if there are lots of unique records, because the summarizer has to then search and sort thru those too. You're still talking about a second or two search time on a fast machine with 100,000 records, depending on the complexity of the search.If you don't want to incur that overhead every time someone hits the page, you can use a technique called 'rendering' discussed on this list: every time your main database changes (hopefully not too often), you would execute a WebDNA template that does the summary once and have it do a [writefile] to create a static HTML page with the completed search results on it. This pre-created page would serve up very fast because no searching would be needed.Similarly, you could 'render' a database that contains all the subcategories rather than rendering a final HTML page. We do this a lot with our hosted sites, where the customer sends us a database that contains updates to their main database -- we use WebDNA to blend the two together and render a final database, complete with categories.I hope this helps,Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | 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)
>Just to make sure I understand correctly, you are saying that if I have about 10 >-20 unique categories, the speed is the same whether or not I have 100, 1000 or >100,000 records? > >Slowness occurs when the # of unique categories increases drastically from 10-20 >to 100's or more?Actually it slows down (as you'd expect) the more items in the database. WebCatalog has to search thru all 100,000 records to find the items to summarize, so naturally it would be faster if there were only 1,000 records to look thru. I think John was saying that there's an extra slowdown if there are lots of unique records, because the summarizer has to then search and sort thru those too. You're still talking about a second or two search time on a fast machine with 100,000 records, depending on the complexity of the search.If you don't want to incur that overhead every time someone hits the page, you can use a technique called 'rendering' discussed on this list: every time your main database changes (hopefully not too often), you would execute a WebDNA template that does the summary once and have it do a [writefile] to create a static HTML page with the completed search results on it. This pre-created page would serve up very fast because no searching would be needed.Similarly, you could 'render' a database that contains all the subcategories rather than rendering a final HTML page. We do this a lot with our hosted sites, where the customer sends us a database that contains updates to their main database -- we use WebDNA to blend the two together and render a final database, complete with categories.I hope this helps,Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

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:

Sort of a Dilemma! (1998) A little syntax help (1997) Great product and great job ! (1997) Next X hits (1996) sandbox is hogging 99% cpu cycles (2004) absolute paths for databases? (1997) Sorting by date (1997) Fun with Dates - revisited (1997) OT : Virus (2000) Not really WebCat- (1997) Math, Multiple Equasions and Show/Hide (1998) Re1000001: Setting up shop (1997) WebCat2: multiple currency support (1997) Highlighting words found in a keyword search (2003) New Site Announcement (1998) Getting Total Quantity (1997) Ampersand (1997) More WebMerch<->MacAuthoriz (1997) controlling user input (1998) CERT Advisory on malicious scripts (2000)