Contains on ResultSet is too slow

[om...@illusivenetworks.com]

Hi,

I'm using HashIndex on several properties with OnHeap persistance.

I use equal query after getting the ResultSet and I noticed that contains function is working pretty slow.

I'm iterating millions of objects and asking on contains for each of them.

What am I missing?

And another question,

If I have a indexed field and I want to ask on a specific object if he's matching a query, 

Should I use the index to get all the matching objects and then ask contains or just use query matches on that object.

[Niall Gallagher]

Could you provide a self contained code snippet which I can run to reproduce the issue, and I'll take a look?

The contains() method indeed should not be slow, if indexes are available.

Thanks,

Niall

           

--
-- You received this message because you are subscribed to the "cqengine-discuss" group.
http://groups.google.com/group/cqengine-discuss
---
You received this message because you are subscribed to the Google Groups "cqengine-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cqengine-discu...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[om...@illusivenetworks.com]

I didn't managed to create a code snippet for that, I think the contains method is not my biggest problem right now.

How about my second question?

Is there a best practice guide I can use? 

[Niall Gallagher]

For your second question, if you want to check if an object matches a query, it's usually more efficient to call query.matches(Object, null).

Best regards,

Niall