{
 "schema_version": 1,
 "generated": "2026-10-31",
 "id": "morluto-flameox--profile-python-benchmark-hotspots",
 "repo": "morluto/flameox",
 "repo_url": "https://github.com/morluto/flameox",
 "repo_slug": "morluto-flameox",
 "title": "Profile a Python benchmark for runtime hotspots",
 "page_title": "How to profile a Python benchmark for runtime hotspots with Flameox",
 "summary": "Capture a benchmark run and get bounded hotspot evidence without a project setup.",
 "who": "A developer who has a slow Python script or benchmark and wants to see where time goes before changing code.",
 "problem": "Profiling output is hard to read and easy to over-interpret, and a manual profiling setup takes time.",
 "outcome": "A bounded evidence result for the run that points to hotspots, with its limitations stated, ready for a hypothesis to be tested.",
 "steps": [
  "Open a terminal in the project folder and note its absolute path with `pwd`.",
  "Run `uvx flameox capture --provider direct --cwd \"$PWD\" -- python benchmark.py` with your own benchmark script in place of benchmark.py.",
  "Read the returned evidence and any `next_page` value; replay a `next_page` continuation using its named analysis tool and arguments unchanged.",
  "Treat the hotspots as exploration leads only; plan a separate experiment before claiming any speedup."
 ],
 "agent_prompt": "Using the flameox repo, capture a profile of <benchmark command> run from the absolute working directory <project path> with `uvx flameox capture --provider direct --cwd <project path> -- <benchmark command>`. Return the bounded hotspot evidence and its stated limitations. Verify that the result states what was observed versus inferred and does not claim causality.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "Flameox records what the profile shows and does not establish causality or performance improvement, so any fix still needs its own measured experiment.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "python",
 "requirements": [
  "Node.js (for npx) or uv (for uvx) installed",
  "Python 3.12 or newer for the local development path",
  "An absolute path to an existing artifact file, or an explicit command to run from an absolute working directory"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": true,
 "score": 1.0,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/morluto-flameox/profile-python-benchmark-hotspots/",
 "md": "https://dedupedai.com/use-cases/morluto-flameox/profile-python-benchmark-hotspots/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/morluto-flameox--profile-python-benchmark-hotspots.json",
 "api_version": "v1"
}