Any advice for the good "size" of a Python buildbot worker?
Hi,
We would like to add more buildbot workers for test Python on Fedora and RHEL, but I have no idea of the ideal "size" of a worker:
- Number of CPUs? I guess that 2 CPUs is nice but 4 or more is better?
- Memory size? At least 8 GB?
- Minimum storage? Logs are sent to the buildbot server, so there is no much stored for long term, no? On my laptop, my python source directory takes around 500 MiB including ".git" repository and object files (.o, .so, python binary, etc.) with Python compiled in debug mode (keep debug symbols) I would say that 10 GiB is nice, 20 GiB is better?
Victor
Night gathers, and now my watch begins. It shall not end until my death.
On Thu, Feb 21, 2019 at 8:06 AM Victor Stinner <vstinner@redhat.com> wrote:
We would like to add more buildbot workers for test Python on Fedora and RHEL, but I have no idea of the ideal "size" of a worker:
It basically comes down to how long you want to wait for results :). The devguide lists [1] 2 cpu, 512 MB RAM and 30GB storage as the preferred minimums, but that may or may not actually be enough anymore, especially on RAM.
For reference, here are stats on my workers (formatting may be destroyed by Gmail, sorry if so):
+-----------------------------------------------------------------------------------------------------+ | | Type | CPU | RAM | Disk (GB) | | | | cores | threads | freq (GHz) | (GB) | Total | Free | +-----------------------------------------------------------------------------------------------------+ | ware-gentoo-x86 | Bare metal | 2 | 2 | 2.6 | 2 | 52 | 37 | | ware-alpine | Docker on physical | 4 | 8 | 3.4-3.9 | 16 | 108 | 66 | | ware-win81-release | Azure VM | 2 | 2 | 2.39 | 14 | 100 | 91 | +-----------------------------------------------------------------------------------------------------+
[1] https://devguide.python.org/buildworker/#required-resources
-- Zach
participants (2)
-
Victor Stinner -
Zachary Ware