Re: [arangodb-google] Re: Request database optimisation

2019-01-15 Thread Killian Janod
Hello! Quick heads up! The new streaming features completely solved my issue! As the dataset is big requesting a big part of it took lots of RAM. This means that I might have managed it LIMIT OFFSET but the query is slow and doing it multiple time was really slow. So using streaming with 3.4 save

Re: [arangodb-google] Re: Request database optimisation

2018-11-16 Thread Killian Janod
Hi Simran, Thank's a lot for answering my questions. I'm sorry I'have been slow to answer back. There was a copy/paste mistake in the Gist. That's why there was an undefined gfi_s. The Gist has been update to reflect better the query. https://gist.github.com/Waateur/6c8c0b2c40d0dfa08cecfe780275cd

[arangodb-google] Re: Request database optimisation

2018-11-12 Thread Simran Brucherseifer
Hi Killian, it would be helpful to see your exact index definitions, some example documents and to know a bit about the data distribution. How many documents end up in one group here on average? COLLECT code=b.code, category_id=b.category_id INTO code_group What do you actually want to retur