[arangodb-google] Re: Faceted Search Performance

Btw, Fyi, first query (AKA: LENGTH(g)) with an index on attribute1 runs almost same as second query (AKA: WITH COUNT). Here, 2nd query with an index takes 4.4 seconds. But it is still, just one facet. Usually you need a bunch, like in my "long" query in very first post. Let me re-write it using

[arangodb-google] Re: Faceted Search Performance

Hi, I tried it myself on my local laptop, and here are the results: Original query: FOR a IN Asset COLLECT attr = a.attribute1 INTO g RETURN { value: attr, count: length(g) } This executes in about 35 seconds with the 8M documents. The execution plan is not ideal, because it will sort the

[arangodb-google] Re: Faceted Search Performance

Thanks Jan for your reply! But, yes, we have tried "2.x old school" approach* WITH COUNT*, as well as brand new* DISTINCT*. Both yields similar sluggish results :-/ -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group

[arangodb-google] Re: Faceted Search Performance

Hi, one of the things to do for improving the query performance is to get rid of the "INTO" clause, as "INTO" will copy all documents found per group into a new variable "g": FOR a in Asset COLLECT attr = a.attribute1 INTO g RETURN { value: attr, count: length(g) } The query without

[arangodb-google] Faceted Search Performance

We are evaluating ArangoDB performance in space of facets calculations. There are number of other products capable of doing the same, either via special API or query language: - MarkLogic Facets - ElasticSearch Aggregations