Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Feature increments to layer_gpu_timeline

Abierto
#29 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@solidpixel ya está trabajando en esto.

Desde el 13/12/2024.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

The following changes were out of scope for the first PR and would make good follow-on increments.

  • Replace JSON with a simple binary packet format, or protobuf, to avoid the memory allocation churn. [ ]
  • Add trackers for VkImage, VkImageView and VkFramebuffer resources so we can determine which images are used in render passes. This allows tagging render passes that render into the swapchain, and tracking compression status.
  • Add trackers for VkBuffer resources for "whole buffer" transfer workload sizing.
  • Add tracker and resource management to capture indirect parameter buffers.- [ ]
  • Document support for arbitrary user string metadata in the protocol to allow custom layers to be used with Streamline visualization.

Completed:

  • Submit time tracking using CLOCK_MONOTONIC_RAW.
  • Add CPU submit time to the layer metadata so we can show the submit-to-execute latency, and sort by submit time not just execution start time. This will be another case where multi-submit command buffers won't work without us wrapping command buffers with a unique submit_id label.
  • Change label metadata to a JSON list to preserve the stack, rather than merging with | separators, as we don't escape the separator if the label contained it. (Done in #40)
  • Improve helper scripts to support gathering logcat files (Done in #41)
  • Improve helper scripts to support gathering Perfetto files (Done in #41)
  • Improve helper scripts to support gathering metadata files (Done in #41)
  • Improve the prototype Python host services server to make it production ready.
Lenguaje dominante
C++
Estrellas
40
Forks
12
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ARM-software/libGPULayers

Todos los issues de ARM-software/libGPULayers

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.