Closed Bug 1473632 Opened 2 years ago Closed 2 years ago

More capacity for tasks on packet.net

Categories

(Taskcluster :: Operations and Service Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gbrown, Assigned: wcosta)

References

Details

I'm using terraform-packet/tc-worker-docker-v1-B4 to run tests on packet.net, but there's only one instance (with concurrency 4, so I can run 4 test tasks at a time). The mobile team is also trying to use these to "green up" tests, so we really need more capacity.

I talked with Jonas about this last week, but I'm not sure where it stands. We thought we'd try 5 instances (20 concurrent tasks).
Wander, can you make this happen?
Flags: needinfo?(wcosta)
(In reply to Geoff Brown [:gbrown] from comment #1)
> Wander, can you make this happen?

Yes, sure I am picking it
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
Flags: needinfo?(wcosta)
I am no longer using terraform-packet/tc-worker-docker-v1-B4 (which did have 5 instances/20 concurrent tasks available recently - thanks!).

With docker-worker (terraform-packet/gecko-t-linux) I can run multiple tests at once: it looks like 10 concurrent tasks. :wcosta, can you confirm that is the expected limit? Is that still 4 containers / instance?
Flags: needinfo?(wcosta)
(In reply to Geoff Brown [:gbrown] from comment #3)
> I am no longer using terraform-packet/tc-worker-docker-v1-B4 (which did have
> 5 instances/20 concurrent tasks available recently - thanks!).
> 
> With docker-worker (terraform-packet/gecko-t-linux) I can run multiple tests
> at once: it looks like 10 concurrent tasks. :wcosta, can you confirm that is
> the expected limit? Is that still 4 containers / instance?

I put 2 containers/instance * 5 instances, just an arbitrary number to check if everything goes ok. Is 4 containers/instance enough?
Flags: needinfo?(wcosta)
Thanks. I think 4 containers/instance is best (reduce cost + consistent with what we sized before).
Component: General → Operations
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Component: Operations → Operations and Service Requests
You need to log in before you can comment on or make changes to this bug.