Re: WC Web* performance (was: Advice on MacOS & TCP...)

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 35470
interpreted = N
texte = Thanks Marty, It sounds like you went through the same things we went through but I am totally 100% absolutely convinced it has something to do with webcat. We tried everything and the only common thread was webcat. When we moved it to the G4 with WebSTAR 3X, everything was fine. The G4 with WS4 hums along and the G4 with WS3 and Webcat hums along and all the little servers are happy. On the other hand, our new webcat 4 seems to run fine under WS4 so it's quickly becoming a moot point to us.Marty Schmid wrote:> Larry wrote: > > >We have several MacOS servers, all running WebSTAR and WebCat. We have > >some database > >activity for Inventory and POS that utilizes TCP connect/sends. We found > >performance > >with WC under WS 4.2X --- how can I say this nicely --- it sucked! > >Stalled is not even > >a good description. It went into a do-nothing mode. ... > > We too had massive performance problems when we upgraded a G4 (Yikes) with > WebStar 4.2 & WC PI 3.08. Performance would start out great but within > hours or minutes would degrade until the server totally stalled on serving > a simple straight html page. We didn't know if it was related to the > upgrade or not because the problem's occurence coincided with a large > increase in traffic. > > Anyway, we did all the typical things in an effort to overcome this, > searched for Gremlins, walked through thousands of lines of code, rebuilt > harddrives, replaced memory modules, changed network hardware, etc. etc. > but nothing helped. We finally pulled out a brand new G4 Sawtooth and tried > that and the problem still occurred. > > Next, I put our entire setup on a G3 Powerbook with a non-velocity version > of Web* 4.2 and things ran great on that machine for the next 24 hours. > > We then went back to the G4s and started pulling out any extension & > control panel we didn't think was absolutely critical and somehow we > happened upon the right combination, performance became phenomenal on the > G4 and the machine has been completely stable and fast for months now. > > I believe that there is some strange combination between WebStar 4.2 and > the default extensions in a G4 that causes WebCat to go into never-never > land, if you back down to Web* 3 you're fine I think. Then again it may not > involve WebCat at all - but we could never generate sufficient traffic on > a pure Web* (non-WebCat) server to see if the problem would occur without > WebCat. > > Wish I had more details on this but you may want to try pulling out > extensions and control panels until the G4 server becomes fast and stable. > Of course YMMV. > > Hope that helps - and thanks for the feedback > Marty Schmid > Artwerks > > ------------------------------------------------------------- > 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 > Web Archive of this list is at: http://search.smithmicro.com/ ------------------------------------------------------------- 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 Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: WC Web* performance (was: Advice on MacOS & TCP...) (Marty Schmid 2000)
  2. Re: WC Web* performance (was: Advice on MacOS & TCP...) (Larry Cline 2000)
  3. Re: WC Web* performance (was: Advice on MacOS & TCP...) (Joseph D'Andrea 2000)
  4. WC Web* performance (was: Advice on MacOS & TCP...) (Marty Schmid 2000)
Thanks Marty, It sounds like you went through the same things we went through but I am totally 100% absolutely convinced it has something to do with webcat. We tried everything and the only common thread was webcat. When we moved it to the G4 with WebSTAR 3X, everything was fine. The G4 with WS4 hums along and the G4 with WS3 and Webcat hums along and all the little servers are happy. On the other hand, our new webcat 4 seems to run fine under WS4 so it's quickly becoming a moot point to us.Marty Schmid wrote:> Larry wrote: > > >We have several MacOS servers, all running WebSTAR and WebCat. We have > >some database > >activity for Inventory and POS that utilizes TCP connect/sends. We found > >performance > >with WC under WS 4.2X --- how can I say this nicely --- it sucked! > >Stalled is not even > >a good description. It went into a do-nothing mode. ... > > We too had massive performance problems when we upgraded a G4 (Yikes) with > WebStar 4.2 & WC PI 3.08. Performance would start out great but within > hours or minutes would degrade until the server totally stalled on serving > a simple straight html page. We didn't know if it was related to the > upgrade or not because the problem's occurence coincided with a large > increase in traffic. > > Anyway, we did all the typical things in an effort to overcome this, > searched for Gremlins, walked through thousands of lines of code, rebuilt > harddrives, replaced memory modules, changed network hardware, etc. etc. > but nothing helped. We finally pulled out a brand new G4 Sawtooth and tried > that and the problem still occurred. > > Next, I put our entire setup on a G3 Powerbook with a non-velocity version > of Web* 4.2 and things ran great on that machine for the next 24 hours. > > We then went back to the G4s and started pulling out any extension & > control panel we didn't think was absolutely critical and somehow we > happened upon the right combination, performance became phenomenal on the > G4 and the machine has been completely stable and fast for months now. > > I believe that there is some strange combination between WebStar 4.2 and > the default extensions in a G4 that causes WebCat to go into never-never > land, if you back down to Web* 3 you're fine I think. Then again it may not > involve WebCat at all - but we could never generate sufficient traffic on > a pure Web* (non-WebCat) server to see if the problem would occur without > WebCat. > > Wish I had more details on this but you may want to try pulling out > extensions and control panels until the G4 server becomes fast and stable. > Of course YMMV. > > Hope that helps - and thanks for the feedback > Marty Schmid > Artwerks > > ------------------------------------------------------------- > 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 > Web Archive of this list is at: http://search.smithmicro.com/ ------------------------------------------------------------- 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 Web Archive of this list is at: http://search.smithmicro.com/ Larry Cline

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:

WebCat2 several catalogs? (1997) passing search criteria (1997) [writefile] (1997) My URL, Your URL (2002) pass a captured value (2004) SiteGuard Admin Feature ? (1997) tricky embedded[showifs/hideifs] (w/ code.. long) (2000) Form Variables (2000) syntax question, not in online refernce (1997) Search problem (2002) Security Issue (1999) UnitShipCost, Formulas.db and passwords (2003) One other big addition... (1997) Re:2nd WebCatalog2 Feature Request (1996) Help! WebCat2 bug (1997) Bad Cookie (1998) Country & Ship-to address & other fields ? (1997) Not really WebCat (1997) Tcp connect (2002) Erotic Sites (1997)