vedithal-amd 0254181f42 [rocprofiler-compute] Analysis Database Schema Improvements (v1.2.0) (#2526)
* Analysis database v1.2.0

* `pc_sampling` and `roofline_data` tables should relate to `kernel` table instead of `workload` table

* Remove `kernel_name` fields in `pc_sampling` and `roofline_data` table

* Add kernel existence check for roofline data to prevent KeyError (#2536)

* Initial plan

* Add kernel existence check for roofline data to prevent KeyError

Co-authored-by: vedithal-amd <191402304+vedithal-amd@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: vedithal-amd <191402304+vedithal-amd@users.noreply.github.com>

* Optimize analysis performance

* Refactor database schema: separate metric definitions from kernels

Reorganize the database ORM to decouple metric definitions from kernel
objects. This improves the schema design by:

- Rename Metric -> MetricDefinition and Value -> MetricValue for clarity
- Move metric definitions from kernel-level to workload-level, since
  metric definitions are shared across kernels
- Update relationships: MetricDefinition belongs to Workload,
  MetricValue
  references both MetricDefinition and Kernel
- Refactor metric_view to join through the new schema structure
- Update test fixtures to use renamed table and class names
- Update documentation with new example output using nbody workload
- Regenerate database schema and views diagrams

* Add min amd max aggregation in kernel_view

* Add primary key id from tables into the view

---------

Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: vedithal-amd <191402304+vedithal-amd@users.noreply.github.com>
2026-01-19 15:25:43 -05:00
2025-10-15 13:57:56 +02:00

ROCm Systems

Welcome to the ROCm Systems super-repo. This repository consolidates multiple ROCm systems projects into a single repository to streamline development, CI, and integration. The first set of projects focuses on requirements for building PyTorch.

Super-repo Status and CI Health

This table provides the current status of the migration of specific ROCm systems projects as well as a pointer to their current CI health.

Key:

  • Completed: Fully migrated and integrated. This super-repo should be considered the source of truth for this project. The old repo may still be used for release activities.
  • In Progress: Ongoing migration, tests, or integration. Please refrain from submitting new pull requests on the individual repo of the project, and develop on the super-repo.
  • Pending: Not yet started or in the early planning stages. The individual repo should be considered the source of truth for this project.
Component Source of Truth Migration Status Azure CI Status Component CI Status
amdsmi EMU Pending
aqlprofile Public Completed Azure Pipelines CodeQL
Continuous Integration
clr Public Completed Azure Pipelines
hip Public Completed Azure Pipelines
hipother Public Completed Azure Pipelines
hip-tests Public Completed Azure Pipelines
rdc Public Completed Azure Pipelines
rocm-core Public Completed Azure Pipelines
rocminfo Public Completed Azure Pipelines
rocm-smi-lib Public Completed Azure Pipelines
rocprofiler Public Completed Azure Pipelines
rocprofiler-compute Public Completed Azure Pipelines Formatting
 rhel-8
tarball
ubuntu jammy
rocprofiler-register Public Completed Azure Pipelines Continuous Integration
rocprofiler-sdk Public Completed Azure Pipelines Code Coverage Integration
CodeQL
Continuous Integration
Documentation
Formatting
Python Linting
Restrictions
Release Compatibility
rocprofiler-systems Public Completed Azure Pipelines Containers
rocprofiler-systems GHCR Packages for CI Images
CPack
Formatting
OpenSUSE
Python Linting
RedHat Linux
Ubuntu Jammy
Ubuntu Noble
rocr-runtime Public Completed Azure Pipelines
roctracer Public Completed Azure Pipelines

Tentative migration schedule

Component Tentative Date

*Remaining schedule to be determined.

TheRock CI Status

Note TheRock CI performs multi-component testing on top of builds leveraging TheRock build system.

The Rock CI


Nomenclature

Project names have been standardized to match the casing and punctuation of released packages. This removes inconsistent camel-casing and underscores used in legacy repositories.

Structure

The repository is organized as follows:

projects/
  amdsmi/
  aqlprofile/
  clr/
  hip/
  hipother/
  hip-tests/
  rccl/
  rdc/
  rocm-core
  rocminfo/
  rocmsmilib/
  rocprofiler/
  rocprofiler-compute/
  rocprofiler-register/
  rocprofiler-sdk/
  rocprofiler-systems/
  rocrruntime/
  rocshmem/
  roctracer/
  • Each folder under projects/ corresponds to a ROCm systems project that was previously maintained in a standalone GitHub repository and released as distinct packages.
  • Each folder under shared/ contains code that existed in its own repository and is used as a dependency by multiple projects, but does not produce its own distinct packages in previous ROCm releases.

Goals

  • Enable unified build and test workflows across ROCm libraries.
  • Facilitate shared tooling, CI, and contributor experience.
  • Improve integration, visibility, and collaboration across ROCm library teams.

Getting Started

To begin contributing or building, see the CONTRIBUTING.md guide. It includes setup instructions, sparse-checkout configuration, development workflow, and pull request guidelines.

License

This super-repo contains multiple subprojects, each of which retains the license under which it was originally published.

📁 Refer to the LICENSE, LICENSE.md, or LICENSE.txt file within each projects/ or shared/ directory for specific license terms. 📄 Refer to the header notice in individual files outside projects/ or shared/ folders for their specific license terms.

Note

: The root of this repository does not define a unified license across all components.

Questions or Feedback?

We're happy to help!

S
Popis
Nebyl uveden žádný popis
Readme 282 MiB
Jazyky
C++ 67.5%
C 20.6%
Python 6.6%
CMake 3.4%
Shell 0.6%
Jiný 1.1%