Push Evaluation Strategy performance issue
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 114
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
If I configure a repository with Push, the performance of the SPARQL query is extremely slow and might not return within timeout.
If I create the same repository but with Push disabled the performance is reasonable.
Background:
- The SPARQL query is very complex (paths, sub-queries etc): would this impact the Push strategy?
- I have Halyard running in a single node configuration: would this also impact use of the Push strategy?
- HBase1.2.6/Hadoop2.7.4/Halyard2.5
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the same complex SPARQL query with Push enabled and disabled in the stated Halyard 2.5, HBase 1.2.6, Hadoop 2.7.4 single-node setup. Investigate whether query complexity or the single-node configuration causes the timeout; done means identifying the cause and documenting the observed performance difference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hadoop, java
- Domain
- databases, distributed-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100