OCI Batch Service is a fully managed service that queues, schedules, and runs batch workloads at scale. It automates provisioning, execution, and cleanup across OCI Compute.
Common uses include image rendering, video transcoding, simulations, data processing and ETL, and other jobs that run in parallel.
You can select CPU shapes and set Oracle Compute Units and RAM to fit each task’s resource needs.
Yes. OCI Batch Service requires you to bring your own images. Pull images from OCI Container Registry and run custom renderers, tools, or scripts.
Jobs enter queues based on the priority policies you define. OCI Batch Service adjusts capacity to match your jobs’ needs and policies so critical work runs first when resources or quotas are limited.
OCI Batch Service integrates with OCI Object Storage and OCI File Storage for inputs and outputs. You can also attach persistent block volumes or file storage to jobs as needed using metadata.
OCI Identity and Access Management policies control access. Logging, auditing, and network controls support governance and least-privilege access.
You can view metrics in the OCI Console, check logs in OCI Logging, and set alerts with alarms and notifications. Use events to trigger automated remediation or downstream steps.
Use the OCI Console, command-line interface, or SDKs to create an OCI Batch Service context and at least one fleet and job pool. Create a task profile, define a job and tasks, link to your container image, set environment variables, and submit.
You pay for the compute, storage, and memory your tasks consume. Tagging and compartments help with cost tracking and governance. Tenancy and compartment-level quota alerts can be configured to monitor consumption. For more pricing information, refer to the OCI cost estimator or your Oracle Sales representative.