Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/build: move packet builders #22407

Closed
s-mang opened this issue Oct 23, 2017 · 4 comments
Closed

x/build: move packet builders #22407

s-mang opened this issue Oct 23, 2017 · 4 comments
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge
Milestone
Unreleased

Comments

@s-mang
Copy link
Contributor

s-mang commented Oct 23, 2017

From Ed @ Packet (ed@packet.net):

We're again reorganizing our donated build hardware, this time to move and consolidate servers into a new "Works on Arm" rack in our New Jersey (EWR1) data center. We're happy to have now dedicated facilities for use for sponsored projects, thanks to support from Arm.

I've created a new machine and reserved it for your account. Unlike the equipment you are currently using, it has 96 cores and 32GB of memory (the existing machine has 128G). We think that it will perform just fine, but be aware that there's less memory in it, and you should plan accordingly.

As soon as it's convenient for you, please move your builds to this new hardware, and release the old 128G machine back to the regular pool. I'm hoping that this will be possible to do before the end of the month.
cc @andybons
@s-mang s-mang self-assigned this Oct 23, 2017
@gopherbot gopherbot added this to the Unreleased milestone Oct 23, 2017
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Oct 23, 2017
@gopherbot
Copy link

Change https://golang.org/cl/72790 mentions this issue: env/linux-arm64/packet: update README with new IP

@bradfitz
Copy link
Contributor

bradfitz commented Nov 1, 2017

Did you decrease the number of builder containers running on this host, now that it has less memory?

@s-mang
Copy link
Contributor Author

s-mang commented Nov 2, 2017

No, I did not.

@bradfitz
Copy link
Contributor

32 GB / 20 builders = 1.6 GB per build. I think that's still acceptable. We run some of the GCE VMs with that much memory.

So, nothing to do here.

@golang golang locked and limited conversation to collaborators Dec 18, 2018
@rsc rsc unassigned s-mang Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@bradfitz @s-mang @gopherbot