[
https://issues.apache.org/jira/browse/SOLR-16812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727535#comment-17727535
]
Jason Gerlowski commented on SOLR-16812:
----------------------------------------
bq. Here is a benchmark of updating using CBOR vs. JSON our films.json
Curious if you've tried with anything larger (e.g. a {{/export}} of a beefier
collection) - at a glance films.json seems a little small (< 1MB) to benchmark
serialization code? Could you elaborate on the benchmark a bit; would love to
try to replicate, play with different datasets, etc.
If CBOR (or avro, arrow, etc.) makes it in and has perf similar to javabin,
does javabin eventually go away? Would be awesome to replace javabin with a
more standard binary format that we don't have to define/maintain, assuming the
perf is equivalent!
> 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: 20m
> 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]
