1473632 - More capacity for tasks on packet.net

Status: RESOLVED FIXED

(Taskcluster :: Operations and Service Requests, task)

Description

[Geoff Brown [:gbrown]]

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).

Comment 1

[Geoff Brown [:gbrown]]

Wander, can you make this happen?

Comment 2

[Wander Lairson Costa]

(In reply to Geoff Brown [:gbrown] from comment #1)
> Wander, can you make this happen?

Yes, sure I am picking it

Comment 3

[Geoff Brown [:gbrown]]

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?

Comment 4

[Wander Lairson Costa]

(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?

Comment 5

[Geoff Brown [:gbrown]]

Thanks. I think 4 containers/instance is best (reduce cost + consistent with what we sized before).