Dual Processor Cluster Contention

| | TrackBacks (0)

Discussion
Found this on the cool Cluster Rant slash based Cluster site.

While the addition of a second CPU seems minimal from a cost perspective, it may lead to false sense of efficiency for the cluster. Indeed, the tests indicate that a program that normally takes 20 minutes on a single CPU node, may take as long as 40 minutes on an active dual CPU node. This situation may be further compounded by the fact that the batch scheduler may place a program on the first or second processor of any node and thus provide the program with a very heterogeneous memory contention environment. (i.e. some nodes may have large memory contention and other may have none.)

0 TrackBacks

Listed below are links to blogs that reference this entry: Dual Processor Cluster Contention.

TrackBack URL for this entry: http://kennethhunt.com/mt/mt-tb.cgi/700

About this Entry

This page contains a single entry by klsh published on March 26, 2003 9:11 AM.

Memory and a $1200 Killer Rig was the previous entry in this blog.

Linux MVS Mainframe Emulator System/370 is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.