John,
Do you have any performance numbers that you can share around your use
of the existing proxy solution? One of the reasons that Thrift is
performant for Accumulo is that messages are batched by the client
library and sent over a smaller number of RPCs. A C++ client will also
need to have
We're running a experiment with multiple local proxies to try to better
understand the batching and bottlenecking issues. Will report back.
jrf
It'd be really cool to see a C++ client -- fully implemented or not. The
increased performance via other languages like you said would be really nice,
but I'd also be curious to see how the server characteristics change when the
client might be sending data at a much faster rate.
My C++ is
I'm all for this- though I'm curious to know the thoughts about maintenance
and the design. Are we going to use thrift to tie the C++ client calls into
the server-side components? Is that going to be maintained through a
separate effort or is the plan to have the Accumulo community officially
Two kinds of gains:
1) single client throughput: the extra RPC hop through the proxy deserializes
and then reserializes the messages. With the proxy running locally the extra
network hop is less of an issue. This was discussed on the user list (see link
earlier in this thread), and 5x slow
