Re: Xserve Recommendations

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 52181
interpreted = N
texte = > > My question to the list is: > In my experience, When I had processor intensive code in a 4.5 setup, > it could bring my server to a stand-still for a bit. With > multi-threading and proper use of "sandboxing" today, how well can one > ward off this circumstance? (this would be the hesitation that I would > have consolidating to one machine, machine goes down, 80 sites go down > (instead of 20)). This was an OS9 machine ? Using OSX the only reason WebDNA will grind to a standstill is if there is an error in your code .. We can be running some intensive code on the server (using 2 CPU's 'top' will show 198% for WebDNA process) and other websites are still served with no problems at all .. If there is an error in your code the server will stop responding .. > Will this handle all 80 websites robustly.. is the question > I have. > :-) > Easily .. ------------------------------------------------------------- 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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Xserve Recommendations ( Brian Wachter 2003)
  2. Re: Xserve Recommendations ( Alain Russell 2003)
  3. Re: Xserve Recommendations ( Alain Russell 2003)
  4. Re: Xserve Recommendations ( Donovan 2003)
  5. Re: Xserve Recommendations ( Clint Davis 2003)
  6. Re: Xserve Recommendations ( Jesse Williams-Proudman 2003)
  7. Re: Xserve Recommendations ( "flingo" 2003)
  8. Re: Xserve Recommendations ( Alain Russell 2003)
  9. Xserve Recommendations ( Clint Davis 2003)
> > My question to the list is: > In my experience, When I had processor intensive code in a 4.5 setup, > it could bring my server to a stand-still for a bit. With > multi-threading and proper use of "sandboxing" today, how well can one > ward off this circumstance? (this would be the hesitation that I would > have consolidating to one machine, machine goes down, 80 sites go down > (instead of 20)). This was an OS9 machine ? Using OSX the only reason WebDNA will grind to a standstill is if there is an error in your code .. We can be running some intensive code on the server (using 2 CPU's 'top' will show 198% for WebDNA process) and other websites are still served with no problems at all .. If there is an error in your code the server will stop responding .. > Will this handle all 80 websites robustly.. is the question > I have. > :-) > Easily .. ------------------------------------------------------------- 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://webdna.smithmicro.com/ Alain Russell

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:

TCPConnect & Post (2002) OT: 800x600 (2003) WebCatalog Mac and cgi-bin (WebSTAR 2.0) (1997) $Append for Users outside the ADMIN group (1997) WEBCAT HIERARCHY (1999) [interpret] inside the db field? (1997) RAM variables (1997) ShipCost Data Base (1998) [WebDNA] [announce] WebDNA Site and Store (2008) PIXO (1997) are we ready to fix random sort? - Or did that already happen? (2000) MOOOOOO (2000) WebCat vs MS SiteServer? (1999) sort problems....bug or brain fart? (1997) taxTotal confusion (1998) Busy WebCatalog (2000) Calculating multiple shipping... (1997) no [search] with NT (1997) [WebDNA] [BULK] Webdna 6.2 and Windows Server 2012 r2 (2020) Best way to handle 404 errors with WebDNA and Web* V (2003)