[
https://issues.apache.org/jira/browse/SOLR-16812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729720#comment-17729720
]
Ishan Chattopadhyaya edited comment on SOLR-16812 at 6/6/23 12:22 PM:
----------------------------------------------------------------------
The test suite is here:
https://github.com/fullstorydev/solr-bench/blob/ishan/javabin-cbor-testing/suites/json-vs-cbor-vs-javabin.json
Prepare binary format key determines the Indexing format, can be json, cbor or
javabin.
was (Author: ichattopadhyaya):
The test suite is here:
https://github.com/fullstorydev/solr-bench/blob/ishan/javabin-cbor-testing/suites/json-vs-cbor-vs-javabin.json
> 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: 50m
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
