Hi, all I'm using thrift in python, I found serialize structure-data in thrift-python is very slow.
I wrote a serialization test on thrift and json, *testing thrift defination:* https://gist.github.com/4465825 https://gist.github.com/4465826 *python testing code:* https://gist.github.com/4465830 *testing data:* https://gist.github.com/4465834 *testing results:* https://gist.github.com/4465853 testing results: > > Test thrift > > start: 1357457502.17 > > File length: 796500 > > File length: 796500 > > File length: 796500 > > File length: 796500 > > File length: 796500 > > File length: 796500 > > File length: 796500 > > File length: 796500 > > File length: 796500 > > File length: 796500 > > end: 1357457509.93 > > elapse: 7.7634768486 > > > > > > Test json > > start: 1357457509.93 > > File length: 217252 > > File length: 217252 > > File length: 217252 > > File length: 217252 > > File length: 217252 > > File length: 217252 > > File length: 217252 > > File length: 217252 > > File length: 217252 > > File length: 217252 > > end: 1357457510.01 > > elapse: 0.0743980407715 > > As the result above, I can't suffer thrift-serialization is slow like this. And my question is: - Did I have wrong usage with thrift? - Or thrift was not design to transport big data(200k, is it big?) Thanks. -- Vincent.Wen
