Packaging and versioning for benchmarking tools and utilities / 基准测试工具和实用程序的打包与版本管理

Aberta
  • Algo errado?
#1,302 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Pouca atividade
Stack de tecnologia
docker, python
Domínio
build-system, release, tooling

Direção de pesquisa

The issue names no files, tests, or entry points. Start by reviewing the existing benchmarking utilities and the team's internal Docker packaging approach, then check with maintainers whether Docker, PyPI, or both fit the project's direction. Done means an agreed official versioning and packaging plan is defined.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Is your feature request related to a problem? Please describe.

My team has been using InferenceX in our automated testing workflow to generate workloads and run benchmarks. The benchmarking utilities are proving to be a critical tool for both simulating workloads and tracking performance metrics. Right now, there doesn't seem to be an official versioning or packaging process for those tools, which makes it trickier to integrate into our testing environment. Currently, we're handling this by packaging them into in an internal Docker image and including the latest commit hash inside the image.

Describe the solution you'd like

Even though the main focus of the InferenceX project is to create timely and reliable benchmarks of the current state of the inference software ecosystem, Official, versioned releases of InferenceX tools and scripts could be useful for the broader community. Are there plans to publish official versioned releases either via a Docker image, a PyPI package, or both? We'd be happy to help start this work by adapting our current packaging work and creating a PR, but we first wanted to check with maintainers and the community to make sure that is consistent with the future direction of the project.

Describe alternatives you've considered

  • Continuing to refine our internal Docker image that vendors InferenceX.
  • Creating and maintaining our own Python package that bundles the InferenceX benchmarking utilities, rather than relying on an official package.

Additional context

Not that I can think of at the moment. We mainly wanted to understand the project's long term goals related to versioning and packaging, and express our willingness to contribute to a broad solution.

中文说明

功能请求：目前 InferenceX 的基准测试工具和脚本缺少官方的版本管理和打包流程，这使得集成到自动化测试环境中变得困难。请求发布官方版本化的工具，可通过 Docker 镜像、PyPI 包或两者发布。提问者愿意贡献代码来推动此工作。备选方案包括继续维护内部 Docker 镜像或自行打包 InferenceX 基准测试工具。

Linguagem predominante
Python
Estrelas
1.9k
Forks
343
Merge médio
2d 40min
PRs com merge (30d)
431

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de SemiAnalysisAI/InferenceX

Todas as issues de SemiAnalysisAI/InferenceX

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.