Gravatar for

Question by lukaskozak, Apr 2, 2015 5:42 AM

How does number of fields in Coveo scale?

Does the number of fields in Coveo scale to RAM needed for indexing/searching in them linearly?

With Sitecore-SOLR integration we have an issue with that. The more fields you put into the index, the more memory it consumes. You end up setting up more nodes and tweaking with the fields a lot. It doesn't scale well for us.

1 Reply
Gravatar for

Answer by Vincent Séguin, Apr 2, 2015 7:34 AM


The fields doesn't impact the RAM at all. It is not stored in RAM. The only thing it can impact is the queries performance. The more fields are on the documents, the longest it takes to stream them on the line.

Gravatar for

Comment by lukaskozak, Apr 9, 2015 3:49 AM

That can be mitigated in coveoQueryFieldPipeline, correct?

Are all the fields stored by default? In our search engine we can explicitly set indexed="true" stored="false" on the field level to avoid storing unnecessary fields when we just want to search on them and vice versa.

Gravatar for

Comment by Vincent Séguin, Apr 9, 2015 7:15 AM

For the pipeline, the coveoQueryFieldPipeline will work for LINQ queries, but not if you're using the JSUI.

And the indexed="true" stored="false" is specific to Lucene/SOLR, it does nothing by Coveo. All the fields are stored by default.

Ask a question