Rename Omniperf to ROCm Compute Profiler (#428)
- Update filenames. - Update executable to `rocprof-compute` - Update update package to `rocprofiler-compute` - Update name in application output and logs - Update name in README files - Update testing and workflows --------- Signed-off-by: Xuan Chen <xuchen@amd.com>
This commit is contained in:
1 parent
2de2faf944
commit
31b4de1a38
379 files changed
+1976
-1843
No files matched your search
@@ -32,7 +32,7 @@ right for you.
|
||||
:width: 800
|
||||
|
||||
.. _core-install:
|
||||
|
||||
|
||||
Core installation
|
||||
=================
|
||||
|
||||
@@ -44,12 +44,6 @@ installation.
|
||||
* CMake ``>= 3.19``
|
||||
* ROCm ``>= 5.7.1``
|
||||
|
||||
.. note::
|
||||
|
||||
Omniperf will use the first version of ``Python3`` found in your system's
|
||||
``PATH``. If the default version of Python3 is older than 3.8, you may need to
|
||||
update your system's ``PATH`` to point to a newer version of Python3.
|
||||
|
||||
Omniperf depends on a number of Python packages documented in the top-level
|
||||
``requirements.txt`` file. Install these *before* configuring Omniperf.
|
||||
|
||||
@@ -72,16 +66,6 @@ following steps illustrate how to install the necessary Python dependencies
|
||||
using `pip <https://packaging.python.org/en/latest/>`_ and Omniperf into a
|
||||
shared location controlled by the ``INSTALL_DIR`` environment variable.
|
||||
|
||||
.. tip::
|
||||
|
||||
To always run Omniperf with a particular version of python, you can create a
|
||||
bash alias. For example, to run Omniperf with Python 3.10, you can run the
|
||||
following command:
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
alias omniperf-mypython="/usr/bin/python3.10 /opt/rocm/bin/omniperf"
|
||||
|
||||
.. _core-install-cmake-vars:
|
||||
|
||||
Configuration variables
|
||||
@@ -142,7 +126,7 @@ Install from source
|
||||
cd build
|
||||
cmake -DCMAKE_INSTALL_PREFIX=${INSTALL_DIR}/{{ config.version }} \
|
||||
-DPYTHON_DEPS=${INSTALL_DIR}/python-libs \
|
||||
-DMOD_INSTALL_PATH=${INSTALL_DIR}/modulefiles/omniperf ..
|
||||
-DMOD_INSTALL_PATH=${INSTALL_DIR}/modulefiles ..
|
||||
|
||||
# install
|
||||
make install
|
||||
@@ -224,30 +208,21 @@ software stack.
|
||||
.. code-block:: shell
|
||||
|
||||
$ sudo apt install omniperf
|
||||
# Include omniperf in your system PATH
|
||||
$ sudo update-alternatives --install /usr/bin/omniperf omniperf /opt/rocm/bin/omniperf 0
|
||||
# Install Python dependencies
|
||||
$ python3 -m pip install -r /opt/rocm/libexec/omniperf/requirements.txt
|
||||
$ pip install -r /opt/rocm/libexec/omniperf/requirements.txt
|
||||
|
||||
.. tab-item:: Red Hat Enterprise Linux
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
$ sudo dnf install omniperf
|
||||
# Include omniperf in your system PATH
|
||||
$ sudo update-alternatives --install /usr/bin/omniperf omniperf /opt/rocm/bin/omniperf 0
|
||||
# Install Python dependencies
|
||||
$ python3 -m pip install -r /opt/rocm/libexec/omniperf/requirements.txt
|
||||
$ pip install -r /opt/rocm/libexec/omniperf/requirements.txt
|
||||
|
||||
.. tab-item:: SUSE Linux Enterprise Server
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
$ sudo zypper install omniperf
|
||||
# Include omniperf in your system PATH
|
||||
$ sudo update-alternatives --install /usr/bin/omniperf omniperf /opt/rocm/bin/omniperf 0
|
||||
# Install Python dependencies
|
||||
$ python3 -m pip install -r /opt/rocm/libexec/omniperf/requirements.txt
|
||||
$ pip install -r /opt/rocm/libexec/omniperf/requirements.txt
|
||||
|
||||
.. _core-install-rocprof-var:
|
||||
|
||||
|
||||
@@ -79,13 +79,6 @@ directory to begin.
|
||||
$ sudo docker-compose build
|
||||
$ sudo docker-compose up -d
|
||||
|
||||
.. note::
|
||||
|
||||
To troubleshoot Docker container build failures related to certificate verification, try
|
||||
disabling any network proxy services on the host system. These proxy services can interfere
|
||||
with OpenSSL's ability to retrieve a correct certificate chain when the container accesses
|
||||
external websites.
|
||||
|
||||
The TCP ports for Grafana (``4000``) and MongoDB (``27017``) in the Docker
|
||||
container are mapped to ``14000`` and ``27018``, respectively, on the host side.
|
||||
|
||||
|
||||
Reference in new issue
Block a user