A simple solution would be to fork
multiple images and use OpenTalk (say) to control them. I’ve used the Server Smalltalk
framework of VisualAge to build a middleware solution based around a Controller
->* Master ->* Slave architecture. Each image is a separate OS process and so
can have its own core. Cheers, Stewart -----Original Message----- In the Cincom Smalltalk Roadmap 2008 i saw the next: _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Stewart,
We have several cases of bulk-testing that follow this pattern. We run a VW7.6 version of our VW5i client headless and use OpenTalk to implement master/slave techniques. However, we’ve found that Opentalk saturates at about 80 slaves. We’re looking at trying multi-tiered arrangement: a master controls no more than 10 slaves, but a master could really be an intermediary: a slave to a “higher” master and an overseer to other slaves. With no trouble we can run a four-tier solution for 1000 clients, which is about 30% more than we need for our testing.
Cheers!
From:
[hidden email] [mailto:[hidden email]] On Behalf Of Stewart MacLean
A simple solution would be to fork multiple images and use OpenTalk (say) to control them.
I’ve used the Server Smalltalk framework of VisualAge to build a middleware solution based around a Controller ->* Master ->* Slave architecture.
Each image is a separate OS process and so can have its own core.
Cheers,
Stewart
-----Original Message-----
In the Cincom Smalltalk Roadmap 2008 i saw the next:
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |