Kaggle / Kaggle/kaggle-environments
Container resource limit settings may be out of date?
- Dominant language
- JavaScript
- Stars
- 452
- Forks
- 190
- Avg merge
- 31m
- Merged PRs (30d)
- 2
Description
https://github.com/Kaggle/kaggle-environments/blob/3441eee12ef10eb83fc3200e30b031b4461e707e/docker/runsc.sh#L2
https://github.com/Kaggle/kaggle-environments/blob/3441eee12ef10eb83fc3200e30b031b4461e707e/docker/bashsc.sh#L2
Looking at some of the postings on Kaggle, I thought that 1.6 CPUs and 8GB memory might be the basic setup now.
https://www.kaggle.com/competitions/connectx/discussion/185212
https://www.kaggle.com/competitions/halite-iv-playground-edition/discussion/186287
https://www.kaggle.com/competitions/google-football/discussion/187381#1031868
https://www.kaggle.com/competitions/halite/discussion/179132#995906
However, I could not find more recent information, so the configuration may be even different now.
Contributor guide
Research direction
Inspect docker/runsc.sh and docker/bashsc.sh at line 2 to identify the configured CPU and memory limits. Verify the current limits against authoritative Kaggle information, then update the settings only if the newer values are confirmed; done means both scripts reflect the verified configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100