It isn't good, nor bad nor average without context. On it's own, one could interpret that 46 seconds as lightning fast, or dog-slow. You'll need to compare it with other JSON parsers out there and time how long it takes them to parse the same data.
Once you've decided that you're either slower or faster than competition and you have some context, you then need to decide if it's too slow for the use in which it is intended.
Only then can you decide whether the performance is good, bad or average :)
I've dropped some JSON parsing performance tests on this GitHub repository, to compare the performances of my experimental parser/deserializer to those of JSON.NET 5.0 r8, and ServiceStack 3.9.59 :
发布评论
评论（3）
没有背景，它不好，不好，也不好。就其本身而言，人们可以将这 46 秒解释为闪电般的快，或者慢如狗。您需要将其与其他 JSON 解析器进行比较，并计算它们解析相同数据所需的时间。
一旦您确定自己比竞争对手慢或快，并且掌握了一些背景信息，您就需要确定它对于其预期用途是否太慢。
只有这样你才能决定性能是好、坏还是一般:)
It isn't good, nor bad nor average without context. On it's own, one could interpret that 46 seconds as lightning fast, or dog-slow. You'll need to compare it with other JSON parsers out there and time how long it takes them to parse the same data.
Once you've decided that you're either slower or faster than competition and you have some context, you then need to decide if it's too slow for the use in which it is intended.
Only then can you decide whether the performance is good, bad or average :)
该站点列出了许多带有计时的解析器。
https://github.com/eishay/jvm-serializers/wiki/
This site lists many parsers with timings.
https://github.com/eishay/jvm-serializers/wiki/
性能与 JSON.NET 5.0 r8 和 ServiceStack 3.9.59 的性能进行比较：
我在此 GitHub 存储库上放置了一些 JSON 解析性能测试，以将我的实验解析器/反序列化器的 com/ysharplanguage/FastJsonParser" rel="nofollow">https://github.com/ysharplanguage/FastJsonParser
I've dropped some JSON parsing performance tests on this GitHub repository, to compare the performances of my experimental parser/deserializer to those of JSON.NET 5.0 r8, and ServiceStack 3.9.59 :
https://github.com/ysharplanguage/FastJsonParser