joesproxyctl efficiency report

For the example file the candidate returns 192 fewer response bytes, with no difference in calls or analyses. No provider usage was supplied.

command · Offline

Before you start

Save the two measurements in a readable local JSON file. Use the same fixture and measurement layer for both runs. You do not need to open JoesProxy or sign in.

Find the bundled CLI on your Mac

Command

joesproxyctl efficiency report --file workflow.json --json

Try a small synthetic input

Save this as workflow.json in your working directory, then run the command above.

{
  "schemaVersion": 1,
  "baseline": {
    "context": {
      "fixture": "catalog",
      "version": "1",
      "environment": "synthetic",
      "measurementLayer": "result"
    },
    "attempts": [
      {
        "id": "read",
        "operation": "catalog-total",
        "outcome": "success",
        "responseBytes": 256,
        "analysisExecutions": 1
      }
    ]
  },
  "candidate": {
    "context": {
      "fixture": "catalog",
      "version": "1",
      "environment": "synthetic",
      "measurementLayer": "result"
    },
    "attempts": [
      {
        "id": "read",
        "operation": "catalog-total",
        "outcome": "success",
        "responseBytes": 64,
        "analysisExecutions": 1
      }
    ]
  }
}

Illustrative usage; your identifiers and available evidence will differ.

What to look for

For the example file the candidate returns 192 fewer response bytes, with no difference in calls or analyses. No provider usage was supplied.

If the result is unexpected

Use a regular local JSON file no larger than 1 MiB. Context mismatch or failed attempts suppress comparative deltas.

Effects and cleanup

Reads the local file and prints a report; no credentials, capture or network access required.

Browse all CLI reference entries →