Skip to content
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.

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

Size limitations #7

Closed
geekscrapy opened this issue Mar 1, 2019 · 2 comments
Closed

Size limitations #7

geekscrapy opened this issue Mar 1, 2019 · 2 comments

Comments

@geekscrapy
Copy link

Has any testing currently been done as to the limitations of the db? Mainly regarding:

  • Maximum number of files
  • Maximum file size
@icedevml
Copy link
Contributor

icedevml commented Mar 4, 2019

Hello,

so far we've got information about 2 TB of data (in total) succesfully indexed with mquery, while still keeping reasonable query time of 3-5 seconds.

When indexing a single file, the size shouldn't matter, because it will never have more than 2^24 of unique trigrams.

I don't think if we've got any more usage data so far.

@msm-code
Copy link
Contributor

Just to expand on this before closing the issue: right now we have much more than 2TB indexed, and query time is still around 5 seconds.

As icedevml has said, there are no limitations for a single file size - but the bigger are your files the less sense it makes for mquery (due to the way it works - at some point it will contain every possible trigram). Hard to say when, but indexing 4GB files is definitely counter-productive, while 10MB files are definitely handled well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants