next up previous contents logomin.gifunespmin.giflogofap1min.jpgReturn to my home page
Next: The Mosix architecture Up: Beowulf, doing supercomputing with Previous: Performance's analysis of Beowulf   Contents

The great flaw of the Beowulf arquitecture

The Beowulf architecture, in the case of an optimal load balancing between the different process of the different nodes, assures the optimal performance of the application at low cost. But, unfortunately, this case is not always the best possible stage. The most common stage is that some nodes has CPU-bounded jobs, some nodes has IO-bounded nodes, and that is in that way because the born and the finish of process. That means that some nodes can be subused meanwhile other nodes might be overloaded.

The scenario can be worse. In the case of nodes of different performance, the most powerful nodes uses to be misused on normal task partitions. And in the case of multiuser environments, the problem is that we have no control about the load of the different nodes.

The best would be having the best of Beowulf clusters, but with load balancing. That is where Mosix clusters plays a great role.


next up previous contents logomin.gifunespmin.giflogofap1min.jpgReturn to my home page
Next: The Mosix architecture Up: Beowulf, doing supercomputing with Previous: Performance's analysis of Beowulf   Contents
David Santo Orcero 2000-11-24