Re: 2 Questions
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 38264
interpreted = N
texte = Thank you for that tip! I've passed it along to my programmer.Ron Parkerron@rjparker.net----- Original Message -----From: John Peacock
To: WebCatalog Talk Sent: Wednesday, August 29, 2001 9:33 AMSubject: Re: 2 Questions> 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.>> HTH>> John>> --> 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/-------------------------------------------------------------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:
Thank you for that tip! I've passed it along to my programmer.Ron Parkerron@rjparker.net----- Original Message -----From: John Peacock To: WebCatalog Talk Sent: Wednesday, August 29, 2001 9:33 AMSubject: Re: 2 Questions> 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.>> HTH>> John>> --> 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/-------------------------------------------------------------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/
Ron Parker
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:
searchable list archive (1997)
[browsername] not working? (1997)
Updating a database once per day - An example (1998)
How much is too much? I can never remember the answer. (2002)
Color (1997)
RE: AccountAuthorizer doesn't seem to work (1997)
SiteEdit Pro Update Announcement (1997)
Sku numbers (1997)
RE: Problem (1997)
country of origin from IPADDRESS??? (2001)
PSC recommends what date format yr 2000??? (1997)
I'm tired of all this! (2000)
price formula (1999)
AOL and [referrer] (2001)
Trouble with formula.db (1997)
[WebDNA] 6.2 Monitor (2012)
Pull down menu for categories (2000)
Oops, my mistake - (was Bad suffix error) (1997)
Add all products to cart at once? (1997)
Quantity/price formula (1998)