Good to know that I'm not just not finding the solution, there simply is
none.
The system is actually dedicated to the job. But the process may, while
working, receive a signal that alters the ongoing job. Like for example
a terminate signal or more data to be taken into consideration. That's
why I
Currently there is no work around this issue. We consider(ed) that
when you run an MPI job the cluster is in dedicated mode, so a 100%
CPU consumption is acceptable. However, as we discussed at our last
meeting, there are others reasons to be able to yield the CPU until a
message arrives. T
Hi,
thanks for answering. Unfortunately, I did try that, too. The point is
that i don't understand the ressource consumption. Even if the processor
is yielded, it still is busy waiting, wasting system resources which
could otherwise be used for actual work. Isn't there some way to
activate an inter
You should look at these two FAQ entries:
http://www.open-mpi.org/faq/?category=running#oversubscribing
http://www.open-mpi.org/faq/?category=running#force-aggressive-degraded
To get what you want, you need to force Open MPI to yield the processor rather
than be aggressively waiting for a message
