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.

Sign up for GitHub

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

Jump to bottom

Add a note about restart required when tuning feeding parameters #3343

Merged
merged 1 commit into from
Aug 28, 2024
Merged

Add a note about restart required when tuning feeding parameters #3343

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions en/reference/services-content.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -910,12 +910,13 @@ <h2 id="feeding">feeding</h2>
<ul>
<li id="feeding-concurrency"><code>concurrency</code>:
A number between 0.0 and 1.0 that specifies the concurrency when handling feed operations, default 0.5.
When set to 1.0, all cores on the cpu can be used for feeding.
When set to 1.0, all cores on the cpu can be used for feeding. Changing this value requires restart of
node to take effect.
</li>
<li id="feeding-niceness"><code>niceness</code>:
A number between 0.0 and 1.0 that specifies the niceness of the feeding threads, default 0.0 => not any nicer than anyone else.
Increasing this number will reduce priority of feeding compared to search. The real world effect is hard to predict as the magic
exists in the OS level scheduler.
exists in the OS level scheduler. Changing this value requires restart of node to take effect.
</li>
</ul>
<pre>{% highlight xml %}
Expand Down