Hi, I have profiled the execution of a single-facet query with the MMFiles engine this morning and I think we will be able to reduce the execution time quite a bit. In my local tests, I have seen improvements of around 40% in case there is a full collection scan (no indexes) and there is a collect/count on a single attribute. Here is the PR with the changes for reference: https://github.com/arangodb/arangodb/pull/3265
However, even with those changes applied (currently they are contained in the PR only) the combined execution time for multiple facet queries will not get below one second. But at least it would be a step in the right direction, and other queries in MMFiles should also benefit from this. Best regards Jan Am Freitag, 15. September 2017 05:51:32 UTC+2 schrieb Roman Kuzmik: > > 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 WITH COUNT and create an index on each facet.... > will see how long it will take. Currently, "as-is" it takes 117 seconds. > > Thanks for looking into this issue. > > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to arangodb+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
