| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Hopefully these arguments will work a little better.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing AWS backend uses system containers backed on to the AWS
hosted NFS service (EFS). This has some advantages, but also some
disadvantages.
Using the EFS service allows building a container on one instance,
with the state being held on the EFS, and then launching a new
instance to run the container. Using EFS also provides persistence, at
least beyond individual EC2 instances.
However, build performance when using EFS is poor compared with a
local store without the overhead of the network latency. Additionally,
the startup speed of the container running off EFS is slow compared to
local storage.
This backend doesn't use EFS, instead the Guix store sits on instance
storage. Rather than using a system container for a Mini Environment,
an Amazon Machine Image (AMI) is built instead. The fast local storage
makes builds faster, and using EBS storage for the Mini Envirnoments
as well as not having the overhead of starting Ubuntu, then starting
the container also makes startup faster.
|
| |
|
|
|
| |
This will enable garbage collection of the Guix store, without
removing things that are still in use.
|
| | |
|
| |
|
|
|
| |
Explicitly use the specified private key where possible. Also, use a
struct for the user, address and private key.
|
| |
|
|
| |
Which seem to be a possibility if the job is forcefully stopped.
|
| |
|
|
| |
Which contains an available_locally? function.
|
| | |
|
|
|
With a service that performs the same function, and use the
MiniEnvironmentJob instead.
|