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

Question about opengrok/docker on large source data #3874

Closed
narugit opened this issue Jan 26, 2022 · 4 comments
Closed

Question about opengrok/docker on large source data #3874

narugit opened this issue Jan 26, 2022 · 4 comments
Labels

Comments

@narugit
Copy link

narugit commented Jan 26, 2022

Hi, I'm new to OpenGrok. Could I ask a question about opengrok/docker?

As described in README#when-not-to-use-it, what could happen when running the indexer on large source data?

The indexer and the web container are not tuned for large workloads.

@ahornace
Copy link
Contributor

As described in README#when-not-to-use-it, what could happen when running the indexer on large source data?

Give it a shot and you will see :) the chances are that it will work properly for your needs. If you start experiencing slow indexing, crashes, or would need more fine-grained configuration, then it would be better to run OpenGrok the "old way".

@vladak
Copy link
Member

vladak commented Jan 27, 2022

I love the 'what could go wrong' questions :-) I guess the answer lies in https://github.com/oracle/opengrok/wiki/Tuning-for-large-code-bases

Besides the obvious stuff like JVM heap (which is definitely addressable in Docker environment), you may run out of file descriptors or HTTP header space. Or simply you may find that the container does not give you enough flexibility w.r.t. configuration (in which case you might want to create your own image based on the official image).

@vladak vladak closed this as completed Jan 27, 2022
@narugit
Copy link
Author

narugit commented Jan 27, 2022

@ahornace

Give it a shot and you will see

Yeah, that is the best way to learn.

slow indexing, crashes

I see. Thank you for the example :)

@narugit
Copy link
Author

narugit commented Jan 27, 2022

@vladak
Thank you for accepting my question ;-)

I guess the answer lies in https://github.com/oracle/opengrok/wiki/Tuning-for-large-code-bases

It's awesome. I'll read it.

Besides the obvious stuff like JVM heap (which is definitely addressable in Docker environment), you may run out of file descriptors or HTTP header space. Or simply you may find that the container does not give you enough flexibility w.r.t. configuration

Thank you again for detailed example.
It gave me an idea of what I needed to pay attention to. I will read the wiki and try to understand it better.

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

No branches or pull requests

3 participants