Thrift is at a significant disadvantage in these tests because the setup of
the test does not allow for Thrift to reuse the Transport and Protocol
instances. This is because the tests mode of operation does not match well
with real RPC behavior. The tests serialize many times repeatedly, more or
less ignoring the output and then deserialize multiple times repeatedly
from a single serialization.
It would be good to find a way to restructure the tests so that Thrift was
not handicapped by this somewhat artificial usage scenario and could
instead have a standing Transport and Protocol instance for serailization
and deserialization (as is commonly be the case in real world RPC over
Thrift) rather than creating new object instances each invocation.
Original issue reported on code.google.com by chad_wal...@yahoo.com on 25 Jun 2009 at 7:42
Original issue reported on code.google.com by
chad_wal...@yahoo.comon 25 Jun 2009 at 7:42