New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

inefficiency of treesearch engines #31

Open

andreasvc opened this issue Feb 8, 2014 · 0 comments

Labels

Owner

andreasvc commented Feb 8, 2014

tgrep2: generally fast, but loads corpus at every invocation, and always returns an exhaustive list of all matches; no support for discontinuous constituents.
xpath / alpinocorpus: memory hungry, no way to cheaply count number of words or constituents (memory leak?).
regex: OK; could get results with single finditer() query per text, if lines are annotated with sentence numbers.

For features related to pagination, a way to search in an arbitrary slice of sentences is useful.

andreasvc added the efficiency label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment