Just a thought: It seems like customerId is the property that should be indexed here. Although if most/all of your customerIds are < 100000, it may still require a large number of records to be scanned in order to calculate the sum. If so, the problem may just be cache size and/or disk throughput. --Eric
On Wednesday, July 29, 2015 at 1:09:23 AM UTC-5, Prakash Hosalli wrote: > > > I tired with indexing on the 'rate' property , but still no luck. > > I tried explain above query and the screenshot attached in the thread. > > Can anyone help on this. > > > On Tuesday, 28 July 2015 21:21:00 UTC+5:30, SavioL wrote: >> >> Hi, >> try putting an index of type NOTUNIQUE_HASH_INDEX on the 'rate' property. >> Have you some improvement? >> >> regards, >> Savio L. >> > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
