In some preliminary benchmarking (on https://github.com/comunica/comunica-feature-reasoning/tree/alpha) I noticed that this reasoner was actually slower on some tasks than HyLAR - this is surprising since the rule-restriction algorithm here uses .match to retrieve relevant data rather than iterating over all of the data which must be converted to and stored to in an array.
Useful paths of enquiry would be:
Testing with different destinations (perhaps try using Graphy over N3)
Testing the algorithm outside of the Comunica engine to see if the problem just comes from various other data transformations that take place (e.g. wrapping in AsyncIterators and Skolemisation on federated data).
In some preliminary benchmarking (on https://github.com/comunica/comunica-feature-reasoning/tree/alpha) I noticed that this reasoner was actually slower on some tasks than HyLAR - this is surprising since the rule-restriction algorithm here uses
.matchto retrieve relevant data rather than iterating over all of the data which must be converted to and stored to in an array.Useful paths of enquiry would be: