-
Notifications
You must be signed in to change notification settings - Fork 779
indexer in 1.7.x still consumes more CPU than in 1.5 #4003
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
Comments
@der-eismann Looks like it is necessary to properly root cause the change. Could you share the details about the indexer run and the overall environment ? Also, what exact 1.7.x version are you using at the moment ? |
I also encountered the same problem. 1.7 indexing is too slow. |
Hi, do you know how to increase the number of threads in opengrok? I think it takes a lot of time to build an index |
Please create separate discussion for that question. |
@vladak sorry for the late reply. We continued running on 1.5 since it was just working™. I tried to investigate a bit again with 1.12 as the usage is still high, however it seems to be related to the whole per-project management that was introduced in 1.6. Our setup consists of 240 Git repositories that are externally updated (automatic removal of archived repos, adding new ones...). So back in 1.5 we only ran it with Now when I remove All I want is to index our 240 Git repos, re-index them every 10 minutes without updating or syncing them and ideally have an overview on the main page. So basically the 1.5 behavior. Any way to achieve that? |
I was hoping that this issue was resolved in the past year, unfortunately it is still the case:

I guess we'll stay forever on the last 1.5 release as it works just fine. Not sure if we need to configure or tune anything, I was hoping for an easy out-of-the-box solution. I even tried to disable the suggester by disabling it in the read-only config, but either it didn't work or it didn't help.
Originally posted by @der-eismann in #3585 (comment)
The text was updated successfully, but these errors were encountered: