Re: database with 10,000+ web pages stored in it?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 26576
interpreted = N
texte = on 1/25/00 8:06 PM, Kenneth Grome at ken@simplewebstores.com wrote:>> A client is going to have a site with 10,000 pages drawn from a>> database. These are not pointers to a database, these are actual>> pages, in a web based administration system. Can web catalog handle>> this kind of volume?> > webCtaalog can handle hundreds of thousands of records. Tens of thousands is> trivial ...> >> The database size would be around 600 megs or>> more. Certainly you wouldn't keep this in RAM.> > why not?> > ================================> Kenneth Grome, WebDNA Consultant10,000 pages = 600megs of information? that is a lot of HTML/Text which isthe only thing you are actually storing in the tab delimited text files (ie:WebCatalog .db files) Images would just be URL's or partial URL's stored inthe database, the images would be in a directory on the HD and would notaffect Webcatalog nor use Ram within Webcatalog. Thing is if you are usingWebcatalog as a Web Administration tool to publish web pages, you are stillA) dynamically searching and displaying the pages from the database or B)writing static HTML page OUT of the Webcatalog database after someonecreates the entries within the web administration (and yes there are timeswhen this is a better way to go then true dynamic pages if your site/datawill work in this fashion (ie: product information pages, research studies,any information which you need updated via a web interface but would in noway benefit from being constantly dynamically generated.I would break up say different product types, or different departments, orsome how break up pages into meaningful groups so if you do indeed end upwith 600megs of data, say maybe 10 databases of 60megs each or 100 databasesof 6megs each... remember webcatalog will load/unload databases that areneeded/less accessed to fit into ram, and yes you can only have 100databases open at one time, but normally will never run into this happening(if you do, it will load and unload databases, which is rather quick :)When you can buy a Gig of ram for less then you use to spend for a gig ofhard drive space, keeping 600megs in a ram based database is very likely,and affordable.-------------------------------------------------------------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:
on 1/25/00 8:06 PM, Kenneth Grome at ken@simplewebstores.com wrote:>> A client is going to have a site with 10,000 pages drawn from a>> database. These are not pointers to a database, these are actual>> pages, in a web based administration system. Can web catalog handle>> this kind of volume?> > webCtaalog can handle hundreds of thousands of records. Tens of thousands is> trivial ...> >> The database size would be around 600 megs or>> more. Certainly you wouldn't keep this in RAM.> > why not?> > ================================> Kenneth Grome, WebDNA Consultant10,000 pages = 600megs of information? that is a lot of HTML/Text which isthe only thing you are actually storing in the tab delimited text files (ie:WebCatalog .db files) Images would just be URL's or partial URL's stored inthe database, the images would be in a directory on the HD and would notaffect Webcatalog nor use Ram within Webcatalog. Thing is if you are usingWebcatalog as a Web Administration tool to publish web pages, you are stillA) dynamically searching and displaying the pages from the database or B)writing static HTML page OUT of the Webcatalog database after someonecreates the entries within the web administration (and yes there are timeswhen this is a better way to go then true dynamic pages if your site/datawill work in this fashion (ie: product information pages, research studies,any information which you need updated via a web interface but would in noway benefit from being constantly dynamically generated.I would break up say different product types, or different departments, orsome how break up pages into meaningful groups so if you do indeed end upwith 600megs of data, say maybe 10 databases of 60megs each or 100 databasesof 6megs each... remember webcatalog will load/unload databases that areneeded/less accessed to fit into ram, and yes you can only have 100databases open at one time, but normally will never run into this happening(if you do, it will load and unload databases, which is rather quick :)When you can buy a Gig of ram for less then you use to spend for a gig ofhard drive space, keeping 600megs in a ram based database is very likely,and affordable.-------------------------------------------------------------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
J Lane
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:
New commands in Final candidate (1997)
Orderfile context problem (1998)
Emailer help....! (1997)
listfiles, moving files (1998)
[SearchString] (1998)
DataBaseHelper Flawed (1997)
Replace Statement (1997)
WebCat b13 CGI -shownext- (1997)
Date Comparison (1998)
Next X hits (1996)
Email notification to one of multiple vendors ? (1997)
RE: [WebDNA] anyone know why webdna kicking out incorrect dates? (2008)
How true is this? (1999)
Superfilous Characters (1998)
Multiple products Multiple price (2000)
Question about replacing words (1998)
Multiple Merchant Accounts? (1997)
CloseDatabase (1997)
Pithy questions on webcommerce & siteedit (1997)
Date stamp and purging (1998)