Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Hudson Disk Space problems solved (for now, anyway)

Greetings,

Yesterday Matt has eliminated hudson-slave2, and hudson-slave1 has been stretched to support 350G of local disk space. It also has been boosted to 28G of RAM and it currently has 6 executor threads.

If projects play nice, the 350G for local workspaces should last us for a long time while offering us decent build performance by using local disk hardware for builds.

Our Hudson instances are virtualized, so we have the capability of adding extra slaves within a short timeframe. However, since Hudson keeps copies of the project workspace on each slave, we think we're better served by having one big slave rather than multiple small ones.

Enjoy!

Denis


Back to the top