[
https://issues.apache.org/jira/browse/SOLR-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743494#comment-16743494
]
Noble Paul commented on SOLR-13007:
-----------------------------------
{quote}Seems like javabin can be quite easily used to send messages to overseer
using the work queues, and then have overseer compute the final cluster state
as JSON.
{quote}
Yes, that was added to support both json and javabin
bq.The messages to the overseer are usually very small, I don't think the gain
will be that much (speed or size)....
Well, the messages are small. But the no:of messages we process are sometimes
1000s every second for a very large cluster. My own benchmark shows that even
for small messages it can be 20% to 30% in encoding decoding. I'm in the
process of making a lot many more improvements to javabin encoding/decoding
and that can make the perf improvements even more significant.
This is a micro optimization. Not very essential and it is not very urgent
> Use javabin instead of JSON to send messages to overseer
> --------------------------------------------------------
>
> Key: SOLR-13007
> URL: https://issues.apache.org/jira/browse/SOLR-13007
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Priority: Major
>
> The messages themselves are ephemeral and the readability is not a big issue.
> Using javabin can:
> * reduce the payload size
> * make processing faster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
