[
https://issues.apache.org/jira/browse/SOLR-16812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727728#comment-17727728
]
Noble Paul commented on SOLR-16812:
-----------------------------------
{quote}Could you elaborate on the benchmark a bit; would love to try to
replicate, play with different datasets, etc.{quote}
The benchmark code is already a part of the PR in
[JUnit|https://github.com/apache/solr/blob/de456e88ae76f0f7c07c9504bf0f2a7badd55202/solr/core/src/test/org/apache/solr/util/TestCborDataFormat.java#L57].
You can just run the test and see the numbers for yourself
{quote}If CBOR (or avro, arrow, etc.) makes it in and has perf similar to
javabin, does javabin eventually go away? {quote}
That should be the goal. Eventually we should get rid of javabin
At the moment, as long as it is faster than JSON it's a win for anyone who uses
non-java clients.
> Support CBOR format for update/query
> ------------------------------------
>
> Key: SOLR-16812
> URL: https://issues.apache.org/jira/browse/SOLR-16812
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Javabin is quite efficient and fast . But non-java users have to use JSON
> exclusively
>
> [CBOR |http://example.com/] is a widely used format that is supported by most
> languages.
>
> Here is a benchmark of updating using CBOR vs. JSON our films.json
> {code:java}
> Payload Size (bytes)
> ============
>
> json : 633600
> cbor : 290672
> javabin: 234520
> time taken to index
> ====================
> JSON: 583ms
> CBOR: 509ms
> JAVABIN : 549
> time takes to query *:* 1100 docs
> ==================================
> json: 92 ms
> javabin : 70ms
> cbor : 63ms{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
