That would be my address, yes. But if this is a large amount of code, I
don't have time to go through it. You really need to narrow it down to
something small which can be easily debugged.
I recommend writing a benchmark which times *only* the parsing and
serialization steps, with protocol
Kent I did bench mark only those steps(parsing and serialization
withthe size of encoded message), the code is not all that vast just
dint want to paste it here due to readability issues..will email it
to your account..Thanks a lot for your response kent
On Sep 10, 11:08 am, Kenton Varda
Since you haven't provided any code it's hard to speculate on what may be
going wrong.
On Wed, Sep 9, 2009 at 3:01 PM, rajesh poorv...@gmail.com wrote:
Hi All,
I ran some performance tests to compare the performance for
serializing-persisting-retrieving-desirializing of my POJOs and