Get help, report and discuss bugs.
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 13 Jan 2016, 06:27
It 's not clear what you mean and if you complain about something.
-
ccwillia
- Posts: 3
- Joined: 13 Jan 2016, 02:56
Post
by ccwillia » 14 Jan 2016, 14:59
Sorry i should have phrased as a question. Is it expected for nzbget to use 100% cpu during NZB checking step? Or do i have something configured wrong?
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 14 Jan 2016, 15:17
If with nzb-checking you mean par-repair then the answer is "yes". That's a feature, NZBGet can use multiple CPU cores on all platforms increasing the repair speed. See
[New Feature] Multithreading par-repair for details and benchmarks.
If you mean something else please be more specific.
Generally you should expect better performance in NZBGet. Where performance means either "do the same job quicker" or "do the same job with less CPU load". NZBGet has a plenty of options allowing you to configure it either for "quicker" or for "less resource hungry". See
Performance tips.
Who is online
Users browsing this forum: No registered users and 51 guests