It seems that mpirun adds /usr/lib64 at the beginning of the
LD_LIBRARY_PATH environment variable (/usr/lib64 usually corresponds to
/usr/lib on non-amd64 systems):
$ env | grep LIB
LD_LIBRARY_PATH=/home/ingo/opt/lib:/home/ingo/opt32/lib:/home/ingo/opt/gcc/lib64
$ mpirun env | grep LIB
LD_LIBRARY
Barry Rountree schrieb:
> On Thu, Apr 24, 2008 at 12:56:03PM +0200, Ingo Josopait wrote:
>> I am using one of the nodes as a desktop computer. Therefore it is most
>> important for me that the mpi program is not so greedily acquiring cpu
>> time.
>
> This is a kern
method that
sleeps not for a fixed time, but until new messages arrive.
Barry Rountree schrieb:
> On Wed, Apr 23, 2008 at 11:38:41PM +0200, Ingo Josopait wrote:
>> I can think of several advantages that using blocking or signals to
>> reduce the cpu load would have:
>>
&
I can think of several advantages that using blocking or signals to
reduce the cpu load would have:
- Reduced energy consumption
- Running additional background programs could be done far more efficiently
- It would be much simpler to examine the load balance.
It may depend on the type of program
I noticed that the cpu usage of an mpi program is always at 100 percent,
even if the tasks are doing nothing but wait for new data to arrive. Is
there an option to change this behavior, so that the tasks sleep until
new data arrive?
Why is this the default behavior, anyway? Is it really so costly
