Re: [WebDNA] Limits?
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102321
interpreted = N
texte = In relation to this topic. One of my production servers has 100 websites on it, all running in each their own sandbox. The server has run solid, without a hiccup for 4 years. In January I notices that my Triggers were being deleted. Randomly. I tried to figure out if there was a pattern to it all, and discovered that they would be deleted between 4:30am - 5:30am right during the height of my backup process. A few weeks later the entire server, all websites, started to experience a 45-50second delay in loading pages. The WebDNA engine was practically halting on every page load. Here's what I figured out: Each of the 100 websites has 120+ databases. Each website had 3 databases dedicated to user tracking (a record of every product and page viewed), that's 300 tracking databases. Of the 300 tracking databases, about 10 of them had reached 300MB+ in size, that's 3GB. I only have 4GB RAM on that server. The massive slow down was caused by the databases needing time to commit, flush and reload. Once I deactivated the tracking on the 10 databases the server immediately went back to normal operations. Getting back to the trigger issue... What I later realized was that during the backup process every night the server creates a zip file of each website and saves it into a temp folder, then transfers it to my backup machine. Whenever the server started the zip of a very large website it was causing a memory overflow and all the WebDNA databases were being pushed out of memory before they could finish committing and flushing. I would find a few empty database files on the websites, but I always found all of my active Triggers.db cleared out. I also would find a partially saved file called Triggers.db.TeMpOr (i can't actually remember the real temporary file name, but it was something like that.) in every Sandbox. This Trigger issue was resolved the same day I fixed the issue with the 300MB databases I described above. Matthew A Perosi JewelerWebsites.com ------------------------------by Psi Prime------- Senior Web Developer 323 Union Blvd. Totowa, NJ 07512 Pre-Sales: 888.872.0274 Service: 973.413.8213 Training: 973.413.8214 Fax: 973.413.8217 http://www.jewelerwebsites.com http://en.wikipedia.org/wiki/Psi_Prime%2C_Inc http://www.psiprime.com Govinda wrote: > I remember back in v.3 days (v.4 too?) the stated limit (from WebDNA's > side) was (IIRC) "maximum of 100 open databases". > Later we were informed something like, 'WenDNA is now so intelligent > in the way that it opens and closes databases that there is > effectively no limit since once the limit is reached then WebDNA > closes one that is not being used and opens the new one being called > so well that to the end user it is as good as 'no limits'. > -G > >> Bob, what gives your customer the impression that there is >> a limit? What is his needs and what is he doing? > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > >
Associated Messages, from the most recent to the oldest:
In relation to this topic. One of my production servers has 100 websites on it, all running in each their own sandbox. The server has run solid, without a hiccup for 4 years. In January I notices that my triggers were being deleted. Randomly. I tried to figure out if there was a pattern to it all, and discovered that they would be deleted between 4:30am - 5:30am right during the height of my backup process. A few weeks later the entire server, all websites, started to experience a 45-50second delay in loading pages. The WebDNA engine was practically halting on every page load. Here's what I figured out: Each of the 100 websites has 120+ databases. Each website had 3 databases dedicated to user tracking (a record of every product and page viewed), that's 300 tracking databases. Of the 300 tracking databases, about 10 of them had reached 300MB+ in size, that's 3GB. I only have 4GB RAM on that server. The massive slow down was caused by the databases needing time to commit, flush and reload. Once I deactivated the tracking on the 10 databases the server immediately went back to normal operations. Getting back to the trigger issue... What I later realized was that during the backup process every night the server creates a zip file of each website and saves it into a temp folder, then transfers it to my backup machine. Whenever the server started the zip of a very large website it was causing a memory overflow and all the WebDNA databases were being pushed out of memory before they could finish committing and flushing. I would find a few empty database files on the websites, but I always found all of my active triggers.db cleared out. I also would find a partially saved file called triggers.db.TeMpOr (i can't actually remember the real temporary file name, but it was something like that.) in every Sandbox. This Trigger issue was resolved the same day I fixed the issue with the 300MB databases I described above. Matthew A Perosi JewelerWebsites.com ------------------------------by Psi Prime------- Senior Web Developer 323 Union Blvd. Totowa, NJ 07512 Pre-Sales: 888.872.0274 Service: 973.413.8213 Training: 973.413.8214 Fax: 973.413.8217 http://www.jewelerwebsites.com http://en.wikipedia.org/wiki/Psi_Prime%2C_Inc http://www.psiprime.com Govinda wrote: > I remember back in v.3 days (v.4 too?) the stated limit (from WebDNA's > side) was (IIRC) "maximum of 100 open databases". > Later we were informed something like, 'WenDNA is now so intelligent > in the way that it opens and closes databases that there is > effectively no limit since once the limit is reached then WebDNA > closes one that is not being used and opens the new one being called > so well that to the end user it is as good as 'no limits'. > -G > >> Bob, what gives your customer the impression that there is >> a limit? What is his needs and what is he doing? > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > >
"Psi Prime, Matthew A Perosi "
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:
Re2: frames & carts (1997)
2nd WebCatalog2 Feature Request (1996)
multiGroupChecker code redundant? (2000)
attaching a file using [sendmail]? (2002)
wrong authentication (1998)
'does not contain' operator needed ... (1997)
[append] problem (1997)
[GREP] Why is the dash invalid? (2002)
TCP Connect (1999)
WebCat2b12 CGI Mac -- Problems propagating the cart through frames...still (1997)
Bug Report, maybe (1997)
ShipCosts database (1997)
Nesting format tags (1997)
Re:quit command on NT (1997)
Emailer (WebCat2) (1997)
Ampersand (1997)
What does this error mean? (2000)
protect tag not working (1998)
F2 to F3 rocky transition (1997)
Here is the code: (2000)