Re: 2 Questions

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 38246
interpreted = N
texte = Ron Parker wrote: > > Howdy everyone :-) > > I'd appreaciate if you can help me with these 2 questions ... > > 1. If I have a database file that's 3 gig's in size. How much memory (RAM) > must webcatalog have on the server to maintain a fast search (speed is > important to me)?This is way too massive a database to use WebCatalog exclusivle. Do you have lots of text fields of enormous size or do you simply have a huge number of records? If the former, do you need to search in every field or are there fields you just return? What I am getting at is that you should not store anything in a WebCatalog database that you don't intend to search in. That can even be generalized to don't store any thing that you are not searching often.For example, a publishing system where you have full text stored (say an entire e-book) but you only need to search a summary. In this instance, store the summary in WebCatalog and store the book itself in a seperate file. If you need to create a summary by the use of a seperate program (say a keyword scanner), still keep the bulk of the text stored outside of WebCatalog and just store the summarized text.If you truly have that many records, I would recommend splitting the database into searchable fields and non-searchable fields. Then store the searchable portion in WebCatalog (ideally would be SKU plus no more than a couple of dozen of small fields), and then store the non-searchable fields in a relational database (MySQL is free, as is PostgreSQL). Use the WebCatalog portion to select which records to display, then retrieve those records only from the external database.Just because WebCatalog is so amazingly flexable and fast, doesn't mean that you should keep all of your data in RAM.HTHJohn-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747------------------------------------------------------------- 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 Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: 2 Questions (Ron Parker 2001)
  2. Re: 2 Questions (John Peacock 2001)
  3. Re: 2 Questions (Kenneth Grome 2001)
  4. Re: 2 Questions (Jason Tyler 2001)
  5. Re: 2 Questions (Andrew Simpson 2001)
  6. 2 Questions (Ron Parker 2001)
  7. Re: 2 questions (Conley Hanson 2000)
  8. Re: 2 questions (Dave MacLeay 2000)
  9. Re: 2 questions (Kenneth Grome 2000)
  10. Re: 2 questions (Kenneth Grome 2000)
  11. Re: 2 questions (Conley Hanson 2000)
  12. 2 questions (Conley Hanson 2000)
Ron Parker wrote: > > Howdy everyone :-) > > I'd appreaciate if you can help me with these 2 questions ... > > 1. If I have a database file that's 3 gig's in size. How much memory (RAM) > must webcatalog have on the server to maintain a fast search (speed is > important to me)?This is way too massive a database to use WebCatalog exclusivle. Do you have lots of text fields of enormous size or do you simply have a huge number of records? If the former, do you need to search in every field or are there fields you just return? What I am getting at is that you should not store anything in a WebCatalog database that you don't intend to search in. That can even be generalized to don't store any thing that you are not searching often.For example, a publishing system where you have full text stored (say an entire e-book) but you only need to search a summary. In this instance, store the summary in WebCatalog and store the book itself in a seperate file. If you need to create a summary by the use of a seperate program (say a keyword scanner), still keep the bulk of the text stored outside of WebCatalog and just store the summarized text.If you truly have that many records, I would recommend splitting the database into searchable fields and non-searchable fields. Then store the searchable portion in WebCatalog (ideally would be SKU plus no more than a couple of dozen of small fields), and then store the non-searchable fields in a relational database (MySQL is free, as is PostgreSQL). Use the WebCatalog portion to select which records to display, then retrieve those records only from the external database.Just because WebCatalog is so amazingly flexable and fast, doesn't mean that you should keep all of your data in RAM.HTHJohn-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747------------------------------------------------------------- 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 Web Archive of this list is at: http://search.smithmicro.com/ John Peacock

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:

Multi-processor Mac info ... (1997) Multiple Passwords (1997) [OT] Apple and 128bit SSL (2003) [ShowNext] feature in 2.0 (1997) SSI *nix 4.5 build (2002) WebSite and *NO* Authentication Dialog Box!!? (1998) WebCatalog vs. Cold Fusion (1998) [WebDNA] Emerging from the Shell (was: unique words) (2009) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) format_to_days on NT (1997) Date Sorting (1997) For those of you not on the WebCatalog Beta... (1997) [WebDNA] Alt Web Servers OS X (2011) [WebDNA] How to generate md5 hash on linux (2009) Pgp&emailer (1997) Wanted: Broader string manipulation functions (1997) Adding a product from another site (1997) normal users.db calls ... (1998) The Box - (2002) WebStar Secure on other machine (1997)