-
Setup:
- Ubuntu 24.04 amd64
- in-tree QAT
- Dual Intel(R) Xeon(R) Gold 6438Y+ (each 16 vfs / total 32)
When i set the worker_processes in the nginx.conf above `32` the qat.service reports `qatmg…
-
### Description
Currently, the behavior of worker process start / end is not well documented. We should document the behavior clearly.
### Link
_No response_
-
When many processes are created, the workers will clog up and keep checking the status of a few processes, without actually running the processes that it depends on.
This is due to the prefetch lim…
-
The [workers](https://github.com/MoveOnOrg/Spoke/tree/master/src/workers) module doesn't have any unit or integration tests yet. We should write some, and continue to update tests when worker behavior…
-
Please document what uwsgi does for workers and processes by default if values are not passed by user
-
### What happened + What you expected to happen
When running on a node with many cores (like >255 cores in a DGX-A100 system), Ray may crash because it cannot create as many threads as it needs.
W…
-
**Am I holding it wrong?**
I'm reading a comment on here, which says to adjust worker process to no more than 24, mine is automatically adjusted to 128, which causes weird things to happen.
http…
figaw updated
2 weeks ago
-
### What is your environment, configuration, and command?
When running idpbuilder in some environment, ingress-nginx never becomes ready because:
```
2024/11/05 17:32:43 [alert] 41#41: pthread_…
-
We've been running into several performance and scaling issues in our production environment lately that are related to sending messages and retrieving their status (or the reports). All of this seem…
-
# Checklist
* [ ] I have verified that the issue exists against the `master` branch of Celery.
* [ ] This has already been asked to the [discussion group](https://groups.google.com/forum/#!forum…