Re: Databases going to sleep
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 19436
interpreted = N
texte = >However.... I recently looked at the visitor analysis page for one of our >virtual sites and it said that there had been no visitors all day. I >opened the log file with a text editor, and discovered that all of the >entries for the past 24 hours were empty-- ie the tabs and return were >there but nothing between them.We do not have a theory about this yet, but there are some things you can do to capture some more information about what's going on. Temporarily turn on the extended error logging (the last popup in your WebCat admin Preferences page). This will write to a file called WebCatalog.debug for *every* hit, before the page is processed. One of the columns contains the number of bytes of RAM available to WebCatalog at the moment of the hit.We do a lot of stuff to clean up whenever we run low on RAM, including commits of open databases, closing databases, stuff like that. Memory can get fragmented on a Mac in a way that leaves little room to work.Once you see the problem again, turn *off* the extended logging so you don't slow your server too much, and then see if there is a correlation between the slowdowns and any info in the log.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>However.... I recently looked at the visitor analysis page for one of our >virtual sites and it said that there had been no visitors all day. I >opened the log file with a text editor, and discovered that all of the >entries for the past 24 hours were empty-- ie the tabs and return were >there but nothing between them.We do not have a theory about this yet, but there are some things you can do to capture some more information about what's going on. Temporarily turn on the extended error logging (the last popup in your WebCat admin Preferences page). This will write to a file called WebCatalog.debug for *every* hit, before the page is processed. One of the columns contains the number of bytes of RAM available to WebCatalog at the moment of the hit.We do a lot of stuff to clean up whenever we run low on RAM, including commits of open databases, closing databases, stuff like that. Memory can get fragmented on a Mac in a way that leaves little room to work.Once you see the problem again, turn *off* the extended logging so you don't slow your server too much, and then see if there is a correlation between the slowdowns and any info in the log.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/
PCS Technical Support
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:
RE: [WebDNA] How to test email validity? (2011)
[Sum] function? (1997)
[WebDNA] Gulf Coast WebDNA programmers (2010)
RE: Formulas.db + Users.db (1997)
security problem (1997)
Online reference (1997)
Mime Headers for Mail (1998)
verify online (1997)
F3 crashing server (1997)
Help name our technology! I found it (1997)
form ENCTYPE confusion (2003)
WebCat2: Items xx to xx shown, etc. (1997)
Stumpted Again (1997)
Help formatting search results w/ table (1997)
Modifying order output (1997)
WebCat2b13MacPlugIn - syntax to convert date (1997)
incrementing a counter remotely? (1999)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
WebDNA Solutions ... sorry! (1997)
Is this possible in simple search? question? (1998)