Google Cloud Batch vs OpenPBS
Google Cloud Batch
cloud.google.comOpenPBS
openpbs.orgSide by side
| Figure | Google Cloud Batch | OpenPBS |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 2 | 1 |
| Spec score · Job Scheduler Software | 8.7 (#3) | 7.8 (#10) |
Plans
In their own words
Google Cloud Batch
Google Cloud Batch schedules, queues, and runs batch jobs on Google infrastructure. It obtains resources for jobs, creates or removes them during runtime to match job specifications, and can scale compute resources automatically for parallel work. Jobs run executable scripts or containerized workloads, with tasks arranged sequentially or in parallel. Storage options include persistent disks, local SSDs, Cloud Storage buckets, and network file systems such as Filestore. Integrations identified for a developer workflow include Cloud Storage, Pub/Sub, Cloud Logging, and Workflows. Batch can send job and task state changes through Pub/Sub, with notifications streamable to BigQuery. It supports IAM permissions and VPC Service Controls; Secret Manager can provide sensitive job data. Batch itself has no additional charge, but resources used by jobs are billed, and quotas and limits apply. Each job is restricted to one task group, named group0, and finished jobs are automatically deleted after 60 days unless deleted earlier. It is available through API and web, with cloud deployment.
OpenPBS
OpenPBS schedules jobs and manages workloads in high-performance computing environments, including clusters, clouds, and supercomputers. Its policy-driven scheduling balances job turnaround time and system utilization while selecting job placements. The system is designed for millions of cores and has been tested beyond 50,000 nodes. A plugin framework provides administration visibility and supports customized extensions. Health checks monitor faults and can mitigate them automatically; the fail-over architecture is designed to avoid a single point of failure and keep jobs running through failures. OpenPBS is self-hosted and free under the AGPL 3.0 open-source license, while PBS Pro is also dual licensed commercially. Public-sector organizations such as academic and research facilities generally choose the open-source license. Community help comes through a volunteer forum, without a guarantee of answers or bug fixes. OpenPBS is integrated into the OpenHPC software stack. The installation guide states that SELinux is not supported, and critical and high security fixes are delivered in the next major release.