Fastjson技术内幕

温少，请教一个问题：
有这样的需求，就是从jsonObject反序列化为javaBean时，需要把yyyy-MM-dd HH:mm:ss格式的字符串转化为
java.util.Date类型，fastjson在1.1.9是不是已经支持了？如果支持了该怎么配置，能给个例子吗？TKS

如果用非常规手段，在特别要求性能的地方，使用缩短包路径，混淆方法名，使其尽可能的短，这样能够提高多少性能？

做了个fastJson与gson对比的压力测试，fastJson性能表现很不错：

Gson:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Document Length:        10304 bytes

Concurrency Level:      400
Time taken for tests:   27.965457 seconds
Complete requests:      40000
Failed requests:        0
Write errors:           0
Total transferred:      414480000 bytes
HTML transferred:       412160000 bytes
Requests per second:    1430.34 [#/sec] (mean)
Time per request:       279.655 [ms] (mean)
Time per request:       0.699 [ms] (mean, across all concurrent requests)
Transfer rate:          14473.75 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    7 146.8      0    3000
Processing:     7  270 213.4    255    2419
Waiting:        6  270 213.2    254    2419
Total:          8  277 257.8    255    3273

Percentage of the requests served within a certain time (ms)
  50%    255
  66%    260
  75%    263
  80%    265
  90%    272
  95%    280
  98%    292
  99%   2370
100%   3273 (longest request)


fastJson:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Document Length:        10304 bytes

Concurrency Level:      400
Time taken for tests:   8.41320 seconds
Complete requests:      40000
Failed requests:        0
Write errors:           0
Total transferred:      414480000 bytes
HTML transferred:       412160000 bytes
Requests per second:    4974.31 [#/sec] (mean)
Time per request:       80.413 [ms] (mean)
Time per request:       0.201 [ms] (mean, across all concurrent requests)
Transfer rate:          50335.64 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    6 141.3      0    3000
Processing:     4   72  10.4     76      94
Waiting:        4   72  10.3     75      94
Total:          5   79 141.8     76    3083

Percentage of the requests served within a certain time (ms)
  50%     76
  66%     79
  75%     81
  80%     82
  90%     84
  95%     86
  98%     88
  99%     89
100%   3083 (longest request)

fastJson在我本机上的速度差不多是gson的10倍！

快一些，但差不多，一个数量级其实都差不多能用，毕竟除了序列化，反序列化外，还有IO输出，业务逻辑处理，他们如果是大头的话，那这点性能差距就微不足道了。

PK功能才是王道

fastjson缺省支持循环引用，这是各个json库中唯一支持的！功能PK，fastjson哪里弱于其他库啊？