Hello,
I've run into an application that has its performance dramatically
affected by some configuration options to the underlying UCX library.
Is there a way to configure/build Open MPI so that which UCX library
is used is determined at runtime (e.g. by an environment module),
rather than having t
ng which can be resolved another way.
>
> --Yossi
>
> -Original Message-
> From: devel On Behalf Of Tim Mattox via
> devel
> Sent: Sunday, 24 January 2021 23:18
> To: devel@lists.open-mpi.org
> Cc: Tim Mattox
> Subject: [OMPI devel] How to build Open MPI so the
gt;
> An other option (I did not try) would be to install UCX on your build
> machine in /usr
> (since I expect /usr/lib/libuct.so is not hardcoded) and then use
> LD_LIBRARY_PATH
> (I assume your ucx module set it) to point to the UCX flavor of your choice).
>
> Cheers,
>
&
t; >
> > Three caveats you should keep in mind:
> > - it is your responsibility to ensure the debug and prod versions of
> > UCX are ABI compatible
> > - it will be mandatory to load a ucx module (otherwise Open MPI won't
> > find UCX libraries)
> > -
; > --enable-params-check --prefix=/same/install/prefix/ucx/1.9.0/debug
> > > > tuned version: --disable-logging --disable-debug --disable-assertions
> > > > --disable-params-check --prefix=/same/install/prefix/ucx/1.9.0/tuned
> > > >
> > > &g
Thank you for the suggestion of 'configure ...
LDFLAGS="-Wl,--enable-new-dtags"'.
I'm still reading up on its meaning, but wouldn't that change the
behavior across all dependencies that are dynamically linked when I
build Open MPI?
I was specifically wanting *just* these UCX .so files to be
dynami
FYI - I wasn’t bothered by the default behavior... I was just looking for a
sanctioned way for an installer (e.g. a sysadmin) to make the UCX be loaded
based on LD_LIBRARY_PATH so that there was an ability for the user to swap
in a debug build of UCX at runtime.
On Mon, Feb 1, 2021 at 10:14 AM Pe
