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

Maxing out CPU (from #535) #544

Open
apcrcom opened this issue Apr 24, 2020 · 9 comments
Open

Maxing out CPU (from #535) #544

apcrcom opened this issue Apr 24, 2020 · 9 comments
Labels

Comments

@apcrcom
Copy link

apcrcom commented Apr 24, 2020

Posted about this recently and thought I had managed to sort it out but the problem is returned.

Cant run Hydra2 without CPU getting maxed out.

https://we.tl/t-X0G8rP7q1h

Tried setting memory to 1024.

Tried bypassing systemd for startup

Pretty much stumped at the moment. Would be grateful for any input.

Thanks

@apcrcom apcrcom added the bug label Apr 24, 2020
@theotherp
Copy link
Owner

Please set the log file level to debug and enable the logging marker "Performance". Restart. Check the system / bugreport tab to see what threads use CPU.

Make a screenshot and attach it with new debug infos. You can attach the files here.

@apcrcom
Copy link
Author

apcrcom commented Apr 24, 2020

Attached. Thankyou.

nzbhydra-debuginfos-2020-04-24-21-08.zip
Screenshot_1

@theotherp
Copy link
Owner

The database is writing a lot of data for some reason. I've had similar reports but haven't been able to reproduce this problem.

If you want you can play around a bit with the database settings:

  1. Create a new folder config in the nzbhydra main folder and in there a file application.properties
  2. Add this line spring.datasource.url=jdbc:h2:file:${nzbhydra.dataFolder:.}/database/nzbhydra;DEFRAG_ALWAYS=TRUE;WRITE_DELAY=20000;RETENTION_TIME=1000.
  3. Try increasing the retention time. I think the default is 45 seconds, so 45000, perhaps choose 20000. Restart Hydra and see if that helps.

@apcrcom
Copy link
Author

apcrcom commented Apr 27, 2020

I did as you suggest and have run it couple days to see how it played out. Looks like its behaving now. Fingers xd.

Thanks for the support. Appreciate it.

@apcrcom
Copy link
Author

apcrcom commented Apr 27, 2020 via email

@theotherp
Copy link
Owner

What values did you use? By the way, they can be configured in the GUI in the latest version (still in beta, though).

You can find donation options on the about page. Cheers.

@apcrcom
Copy link
Author

apcrcom commented Apr 27, 2020 via email

@theotherp
Copy link
Owner

So you just changed the retention time from 1000 to 20_000? Cool...

@jnpeterson
Copy link

I've been having the same issue here - NZBHydra pegging the java process from 25-60% of the CPU consistently. I found this thread and set the logs as suggested and found my MVStore thread was pegged out as well. Followed the instructions given and changed the retention to 20000 and restarted. Now the java process is sitting between about 1-4%. Many thanks for this, it was slowing things down!

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