On Mar 11, 9:42 am, Jon Skeet sk...@pobox.com sk...@pobox.com
wrote:
There's still an optimisation I want to make in terms of unknown field
sets, which made a difference to the C# code, but this result is
really amazing...
Indeed, the Server JIT has a much wider set of optimisations at its
On Mar 6, 1:13 am, Justin Azoff justin.az...@gmail.com wrote:
I did a quick port to python(pasted at the end, hopefully it wont be
garbled)
well, that didn't work.
I threw it up at http://bouncybouncy.net/ramblings/files/ProtoBench.py
if anyone is interested.
--
- Justin
On Mar 6, 1:24 pm, Justin Azoff justin.az...@gmail.com wrote:
On Mar 6, 1:13 am, Justin Azoff justin.az...@gmail.com wrote: I did a
quick port to python(pasted at the end, hopefully it wont be
garbled)
well, that didn't work.
I threw it up
Hi Jon,
On Mar 5, 11:07 am, Jon Skeet sk...@pobox.com wrote:
I haven't optimised with a profiler very recently - I suspect there
are some improvements which could be made by skipping the null
handling when merging/parsing (as it should be unnecessary). I didn't
use any particular options
On Mar 5, 11:47 am, ijuma isma...@gmail.com wrote:
I haven't optimised with a profiler very recently - I suspect there
are some improvements which could be made by skipping the null
handling when merging/parsing (as it should be unnecessary). I didn't
use any particular options when
I appreciate this, as i've been wanting to see some benchmarks between
the implementations for a long time. Of course, as a C advocate (i'm
the author of protobuf-c), I'm hoping (and frankly expecting) that
it'll win in the size AND speed category.
I also like the style of separating the test
On Mar 5, 6:07 am, Jon Skeet sk...@pobox.com wrote:
I've just committed the first pass of a benchmarking tool to trunk.
Everything is under benchmarks - see the readme.txt for usage
guidelines.
Cool :-)
I did a quick port to python(pasted at the end, hopefully it wont be
garbled), my results
