wolfpld / wolfpld/tracy

Can the client query its own statistics?

Open
#992 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
16.8k
Forks
1.2k
Avg merge
1d 19m
Merged PRs (30d)
9

Description

I have been enjoying Tracy for analyzing a read-mapping tool which is reporting stats on its execution. Since these stats are already computed by Tracy too, I am wondering if there is a simple way for the client to self-report some of the Tracy stats. I suppose this will require the client to bring up a server itself.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing Tracy's existing statistics and the client/server architecture, then clarify how a client would query or self-report those statistics and whether it must host a server; done means a defined, agreed approach for that capability.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.