We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Scenario Deploy a docker container with the latest haystack ui tag and specify a cpu limit.
Expected The Node process respects the resource limits and only sees the number of cpus allocated.
Actual The Node process sees all the cpus of the host.
Notes The problem affects the performance of the server by doing an unnecessary number of forks here:
haystack-ui/server/utils/server.js
Line 55 in ee08389
I believe this is similar to this issue that affects Java containers.
If Node does not provide a solution a possible workaround would be to expose the number of cpus as a property and allow users to override it.
The text was updated successfully, but these errors were encountered:
@kapilra : Can you have a look at this.
Sorry, something went wrong.
No branches or pull requests
Scenario
Deploy a docker container with the latest haystack ui tag and specify a cpu limit.
Expected
The Node process respects the resource limits and only sees the number of cpus allocated.
Actual
The Node process sees all the cpus of the host.
Notes
The problem affects the performance of the server by doing an unnecessary number of forks here:
haystack-ui/server/utils/server.js
Line 55 in ee08389
This is worse when running in a highly virtualized platform like Kubernetes where it's common to define cpu (and memory!) limits for each container.
I believe this is similar to this issue that affects Java containers.
If Node does not provide a solution a possible workaround would be to expose the number of cpus as a property and allow users to override it.
The text was updated successfully, but these errors were encountered: