In article <[EMAIL PROTECTED]>, Jeff Schwab <[EMAIL PROTECTED]> wrote: > >Sure, multiple machines are probably the right approach for the OP; I >didn't mean to disagree with that. I just don't think they are "the >only practical way for a multi-process application to scale beyond a few >processors," like you said. For many (most?) applications in need of >serious scalability, multi-processor servers are preferable. IBM has >eServers available with up to 64 processors each, and Sun sells E25Ks >with 72 processors apiece. I like to work on those sorts of machine >when possible. Of course, they're not right for every application, >especially since they're so expensive.
Do these use shared memory? -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ The way to build large Python applications is to componentize and loosely-couple the hell out of everything. -- http://mail.python.org/mailman/listinfo/python-list
