sbp commented on issue #411: URL: https://github.com/apache/tooling-trusted-releases/issues/411#issuecomment-3632603075
Further testing by @alitheg revealed that this also caused an issue with Java starting. GCed languages pre-allocate lots of virtual memory, e.g. "[golang malloc.go allocates 512GB heap for 64bit system](https://groups.google.com/g/golang-nuts/c/FCMPvaBMaMg)", and our resource limits in `worker.py` are for virtual memory rather than resident memory. Therefore we'd have to find an alternative strategy to constrain the resources of our workers if we want to keep such limits. We're considering using containers for the worker tasks, but we'd have to either use Docker in Docker (which currently requires an alternative, experimental runtime), or allow the container to orchestrate tasks on the host. Another possibility is that we could just move the orchestration out of the server entirely. It may be possible to make the tasks themselves self-orchestrating. It doesn't seem advisable to just drop resource limits. Alternatively, of course, we are considering pushing some tasks to GitHub. As long as we can keep our remaining tasks under control this could be fine, but it does mean that bugs could starve the system of CPU or RAM. We should also probably think about inode limits etc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
