Re: [WebDNA] Limits?

This WebDNA talk-list message is from

2009

It keeps the original formatting. numero = 102331
interpreted = N
texte = Great catch Matthew!Psi Prime, Matthew A Perosi wrote:> 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 Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Limits? (rupert ravens 2009)
Re: [WebDNA] Limits? (christophe.billiottet@webdna.us 2009)
Re: [WebDNA] Limits? ("Psi Prime, Matthew A Perosi " 2009)
Re: [WebDNA] Limits? (rupert ravens 2009)
Re: [WebDNA] Limits? ("Psi Prime, Matthew A Perosi " 2009)
Re: [WebDNA] Limits? (Donovan Brooke 2009)
Re: [WebDNA] Limits? (Dale - Ehome 2009)
RE: [WebDNA] Limits? ("Olin Lagon" 2009)
Re: [WebDNA] Limits? (Bob Minor 2009)
Re: [WebDNA] Limits? ("Psi Prime, Matthew A Perosi " 2009)
RE: [WebDNA] Limits? ("Michael A. DeLorenzo" 2009)
Re: [WebDNA] Limits? (Govinda 2009)
Re: [WebDNA] Limits? (Donovan Brooke 2009)
Re: [WebDNA] Limits? (christophe.billiottet@webdna.us 2009)
[WebDNA] Limits? (Bob Minor 2009)

Great catch Matthew!Psi Prime, Matthew A Perosi wrote:> 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 Dale - Ehome

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] Limits?

2009

Top Articles:

Related Readings: