Known issues for Python profiling

There are a few known issues for Python profiling.

• Linaro MAP requires a significant amount of time to analyze samples when profiling a Python script that imports modules which use OpenBLAS, such as NumPy. This is caused by the lack of unwind information in OpenBLAS. This results in partial trace nodes being displayed in Linaro MAP.

• mpi4py uses some MPI functions that were introduced in MPI version 3. For example MPI_Mrecv. Linaro MAP does not collect metrics from these functions, therefore MPI metrics for mpi4py will be inaccurate. To workaround this, use a custom Python MPI wrapper that only uses functions that were available before MPI version 3.

• When using reverse connect (--connect) and quick start (--start) in conjunction, the full path to the Python application must be provided.