Re: WC2.0 Memory Requirements

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 10261
interpreted = N
texte = >Does anyone have any experience with the additional memory overhead when >splitting a database file into 2 or more with WC 2.0. ClubMac appears to >be running several large WC databases - does anyone know the memory >configuration of their server. Actually the RAM usage is less on WC2, because you're not forced to have all 27 fields in a database. There is some overhead involved for every field added to a database, so if you keep it down to the minimum necessary fields you will save a lot of RAM. Here's the RAM equation for a single database: (size of db file on disk) + (#records * #fields * 4)Having 2 separate db files open is no different than having 1 db file containing both databases. Except it's faster to search just the 1 database you're interested in.>I have also noticed some comment on the Webstar list about WC loading >another copy of the databases when a Webstar SSL transaction is invoked. This only applies to plugins. If you run WC2 as a CGI it's not an issue. And we're working on a plan to get plugins working the same way (probably not until the following release though).Grant Hulbert, V.P. Engineering | Tools for WebWarriors Pacific Coast Software | WebCatalog, WebCommerce Solution 11770 Bernardo Plaza Court, #462 | SiteEdit, SiteCheck, PhotoMaster San Diego, CA 92128 | 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: WC2.0 Memory Requirements (Grant Hulbert 1997)
  2. Re: WC2.0 Memory Requirements (Rob Schmidt 1997)
  3. Re: WC2.0 Memory Requirements (Grant Hulbert 1997)
  4. WC2.0 Memory Requirements (plake 1997)
>Does anyone have any experience with the additional memory overhead when >splitting a database file into 2 or more with WC 2.0. ClubMac appears to >be running several large WC databases - does anyone know the memory >configuration of their server. Actually the RAM usage is less on WC2, because you're not forced to have all 27 fields in a database. There is some overhead involved for every field added to a database, so if you keep it down to the minimum necessary fields you will save a lot of RAM. Here's the RAM equation for a single database: (size of db file on disk) + (#records * #fields * 4)Having 2 separate db files open is no different than having 1 db file containing both databases. Except it's faster to search just the 1 database you're interested in.>I have also noticed some comment on the Webstar list about WC loading >another copy of the databases when a Webstar SSL transaction is invoked. This only applies to plugins. If you run WC2 as a CGI it's not an issue. And we're working on a plan to get plugins working the same way (probably not until the following release though).Grant Hulbert, V.P. Engineering | Tools for WebWarriors Pacific Coast Software | WebCatalog, WebCommerce Solution 11770 Bernardo Plaza Court, #462 | SiteEdit, SiteCheck, PhotoMaster San Diego, CA 92128 | 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:

Is there a max number of fields? (1998) Exclamation point (1997) [REPLACE] inside [FOUNDITEMS] (1998) Formatting a .txt file (1998) Searching for words equal to A or equal to B (1999) Multiple Selections in Pull-Down Menu (2000) Cold Fusion Buster (1997) WebCat & cookies (1998) Some Advise needed (1997) 2.0 Info (1997) WebCat2b13MacPlugIn - More limits on [include] (1997) [SearchString] problem with [search] context (1997) SetHeader not Working (2006) [WebDNA] curl and ssl not working (2011) WebCatalog can't find database (1997) Re:WebCat Contest (1998) Re:quit command on NT (1997) Don't tick me off :) [elaspedtime] (1997) ShipCost Problems (1998) Extra carriage returns (1999)