I attached a little performance test on Bug 673039. Really JSON needs more, and it needs to cover a reasonable range of variations (e.g., take the financial input that Kraken uses, and then tweak it, e.g. by adding an "interesting" unicode character to the string. (Of course the test won't even work until Bug 673039 is fixed.) See also Bug 649800, but I think that only added acceptance tests, not performance ones. (But I could be wrong about that, that's why I said "probably" in this bug's title.
I highly recommend seeking out pre-existing JSON test cases that are out there in the wild. (I made an artificial inptut for Bug 640711, but that's not as good as real data that people are using out there.) Example of data from the wild: http://api.t.sina.com.cn/statuses/public_timeline.json?source=2040666075
Another example of data from the wild: http://api.kongregate.com/badges.json (This one is what motivated Bug 672484)
Dan, can you tackle this loose end for i9.
Assignee: fklockii → dschaffe
Priority: -- → P3
Target Milestone: --- → Q1 12 - Brannan
You need to log in before you can comment on or make changes to this bug.