Re: Cluster computing drawbacks


In article <42E63A20.1060309@xxxxxxxxxxx>,
CJT <abujlehc@xxxxxxxxxxx> writes:
|> >
|> > Most people's experience is that it is EASIER than converting
|> > a serial program to use SMP communication. Seriously. Converting
|> > to use SMP is one of the foulest tasks that you can imagine, and is
|> > enought to make you wake up in the middle of the night screaming and
|> > dripping with sweat.
|> >
|> With all due respect, now YOU are making claims you have not justified.

Yup. But I can justify it, from personal experience, from talking
to some of the leading SMP users and from the near-absence of
scalable SMP results from the Web pages of major applications.


Regards,
Nick Maclaren.
.

Relevant Pages

  • Re: Cluster computing drawbacks
    ... |>>> a SMP system will run a lot of software off the shelf with good ... |>> communication, but not so easily using an MPI one. ... but still easier than converting to use SMP communication. ...
    (comp.arch)
  • Re: Cluster computing drawbacks
    ... |>>> a SMP system will run a lot of software off the shelf with good ... |>> communication, but not so easily using an MPI one. ... but still easier than converting to use SMP communication. ...
    (comp.arch)
  • help? converting to single global prio_array in scheduler, ran into snag
    ... We're having some issues with the load balancer algorithm in CKRM, so due to time pressure I'm looking at converting the scheduler to use a single global prio_array rather than the per-cpu ones that it currently uses. ... So far I've removed arrays/expired/active from the runqueue and made them global, added a new spinlock to protect the global list (always taken after the runqueue lock), and converted all the callers to use the appropriate variable. ... This builds for both UP and SMP, boots for UP, and boots for SMP if I set the "nosmp" boot arg. ...
    (Linux-Kernel)