GCP Service Quotas
Google Cloud imposes default quotas on services for all new projects and new accounts, and in specific regions. It is very important to check your current quotas & limits prior to starting your CloudyCluster environment. Low quotas are one of the more common issues clients encounter with CloudyCluster.
Quotas are visible in the console, and they may need to be increased. If your CloudyCluster configuration exceeds the limits, your cluster will not spin up and will roll back. See GCP Service Quotas KB for more information or to request a limit increase.
We recommend requesting additional quota capacity in the following areas:
- Compute Engine API CPUs
- Regional Default: 24
- New: 48
- Enter a brief description, such as: “Testing new job scripts that require more CPUs.”
The approval process is usually less than 24 hours.
Note: Not all machine types and processors are available in all regions. We recommend checking with Google if you are uncertain which machines have the resources you plan on using for your project. Machine Types CloudyCluster has been test validated on N2, C2 and E2 machine types.
Prior to starting your CloudyCluster setup, you should know the basic requirements for your HPC tasks. The size of your job and your desired time to results will determine the types and quantities of resources needed to run your job. Example: (n)nodes = x (n)tasks per node = y (n)CPUs or GPUs
If you don’t know the resources required, you can start with one of the CloudyCluster Quick Start configurations and try it out to get a feel for what you need to complete your job within your desired time frame. You may also contact CloudyCluster Services Team for guidance. support [@] cloudycluster.com