Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Request permission to use InferenceX benchmark results in ConfigIQ

Aperta
  • Qualcosa non va?
#4,655 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
18/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python, pytorch
Ambito
data, documentation

Direzione di ricerca

This is a licensing and permission question rather than a code change: the issue asks whether SemiAnalysis approves private storage, public attributed display, and weekly API refresh of benchmark results, and it points to the API docs and Section 7 of the general terms. A newcomer would read the linked terms and API documentation and check for any stated license, attribution or rate-limit rules. Done means a maintainer has answered the permission question in the thread.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Hi InferenceX team,

The ConfigIQ team is developing a Compare page that shows measured inference performance alongside AISimulators predictions across concurrency levels.

We would like to add InferenceX as a separately labeled measurement source on ConfigIQ’s comparison page. If approved, we propose to:

  1. Fetch selected published single-turn 8192-input / 1024-output-token results using /api/v1/availability, /api/v1/views/options, and /api/v1/benchmarks.
  2. Normalize the selected results and store them in a private Hugging Face dataset so ConfigIQ can load configuration options.
  3. Display selected measurements on ConfigIQ’s public comparison charts alongside our measurements and AISimulators predictions. We would clearly attribute the data to InferenceX/SemiAnalysis and link to the original benchmark runs. The private dataset would not be offered as a public download.
  4. Refresh the private dataset from your API approximately once a week.

The API documentation describes accessing and exporting data for analysis, but we could not determine whether it permits this specific workflow. Section 7 of SemiAnalysis’s general terms also raises a question about scheduled API collection.

Would SemiAnalysis approve these uses: private storage of a normalized subset, public display of selected measurements with attribution, and a weekly API refresh? Are there license, attribution, or request-frequency requirements we should follow? Thanks.

Lingua principale
Python
Stelle
1.9k
Fork
343
Merge medio
2g 40m
PR unite (30g)
431

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di SemiAnalysisAI/InferenceX

Tutte le issue di SemiAnalysisAI/InferenceX

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.