Spawn pools

[smashwilson]

The job runner will happily spawn a goroutine and a container for as many jobs as you throw at it. It would be more prudent to apply some kind of rate-limiting to the jobs that are consumed by a single runner.

[rgbkrk]

I was kind of hoping we adopted the spawn pools aspect of tmpnb and only run jobs for available containers.

[smashwilson]

Oh yeah! That would work as well.

It gets tricky once we start supporting multiple languages (or layers). We might need to have separate pools of each image type (configurable on the fly through the admin interface?) and allow some slop space for runs of ad-hoc images if we guess wrong about the allocation.