Here a live example
[yago@dev-1 ~]$ time curl -g
"http://dev-1:8983/solr/collection-perf/query?rows=0&q=date:[20150101%20TO%2020150115]&json.facet={label:{type:terms,field:url_encoded,limit:-1,sort:{index:asc},facet:{user:'hll(user_id)'}}}"
> dump
% Total % Received % Xferd Average
The collection is a 12 shards distributed to 12 physical nodes (24G heap each,
32G RAM) (no replication). all cache are disable in solrconfig.xml, The rate of
indexing is about 2000 docs/s, this transform cache useless
At the time of the perf test the amount of docs were 34M (now is 54 but t
On Tue, Dec 22, 2015 at 6:06 AM, Yago Riveiro wrote:
> I’m surprised with the difference of speed between DV and stream, the same
> query (aggregate 7M unique keys) with stream method takes 21s and with DV is
> about 3 minutes ...
Wow - is this a "real" DV field, or one that was built on-demand
Ok,
I’m surprised with the difference of speed between DV and stream, the same
query (aggregate 7M unique keys) with stream method takes 21s and with DV is
about 3 minutes ...
—/Yago Riveiro
On Tue, Dec 22, 2015 at 1:46 AM, Yonik Seeley wrote:
> On Mon, Dec 21, 2015 at 6:56 PM, Yago Riv
On Mon, Dec 21, 2015 at 6:56 PM, Yago Riveiro wrote:
> The json facet API method "stream" uses the docvalues internally for do the
> aggregation on the fly?
>
> I wan't to know if using this method justifies have the docvalues configured
> in schema.
It won't use docValues for the actual field be
