Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] query performance

It's a customized repository inherited from AbstractMetadataRepository, but not implements IIndexProvider interface.

I'll add index capability for that repository, then have a try again.

Mengxin Zhu

On 08/10/2011 02:21 PM, Thomas Hallgren wrote:
On 2011-08-10 08:12, Mengxin Zhu wrote:
Hi Thomas,

Thank you for analyzing the bottleneck of my query.

RequiredCapability doesn't support 'namespace' member. So I used below query expression for testing,

"$0.traverse(set(), _, { cache, parent | parent.requirements.unique(cache).collect(rc | select(iu | iu ~= rc)).flatten()})"

However the result is amazing. It costs much more time to query the great number of IUs. I updated the document and benchmark spreadsheet listed below. What do you think?

It looks like the query performs sequential scans instead of using indexes. What type of repository is the 'allIUs' it that you're querying? I'm curious because it doesn't seem to be capable of producing indexes.

- thomas

p2-dev mailing list

Back to the top