Jetstream2 Large Memory, also referred to as Jetstream2 LM, is a cloud-based computing resource that provides on-demand virtual machines with increased memory capacity for data-intensive applications. It is designed for workloads that require more memory than standard CPU instances but do not require GPU acceleration.
Large Memory instances use r3.* flavors. The official Jetstream2 Large Memory flavors include r3.large with 64 vCPUs and 500 GB RAM, and r3.xl with 128 vCPUs and 1000 GB RAM. These instances are suitable for workloads such as in-memory databases, large-scale data analytics, genomics, graph processing, and other high-RAM research applications.
Like other Jetstream2 resources, users manage their own virtual machine environments, including the operating system, software stack, storage attachments, and runtime configuration.
Jobs
Jetstream2 Large Memory does not use a centralized job scheduler. Workloads are run directly on virtual machines created by the user.
Users execute workloads interactively, through scripts, containers, services, notebooks, or other software installed inside the VM environment. For example:
python analysis.pyIf batch scheduling is required, users may deploy and manage their own scheduler or orchestration layer, such as Slurm or Kubernetes, within their virtual infrastructure.
Jetstream2 Large Memory uses r3.* flavors, and resource usage is based on VM flavor size and runtime rather than queued jobs. Users should shelve instances when they are not in use to conserve SUs.
Queue specifications
| Name | Purpose | CPUs | GPUs | RAM | Jobs
30 days
|
Wait Time
30-day trend
|
Wall Time
30-day trend
|
|---|---|---|---|---|---|---|---|
| Indiana Jetstream2 Large Memory | Large-memory virtual machine flavors; not a Slurm partition | AMD Milan 7713; 64 or 128 vCPUs depending on r3 flavor | 500 GB (r3.large) or 1000 GB (r3.xl) VM RAM | — | — | — |
Storage
File System
| Directory | Path | Quota | Purge | Backup | Notes |
|---|
External Storage
Storage Filesystems
Jetstream2 does not use traditional shared HPC file systems. Storage is managed through cloud-style storage resources attached to or accessed from virtual machines.
Instance Storage
- Root or local disk associated with a VM instance.
- Useful for operating system files, installed software, temporary data, and runtime files.
- Data on an instance root disk can be lost when the instance is deleted, depending on how the instance was created.
Persistent Volumes
- Block storage volumes that can be attached to VM instances.
- Useful for datasets, results, database storage, larger working directories, and custom boot disk sizes.
- Volumes are generally attached to a single active instance at a time.
- Volumes can be detached and reattached to another instance when needed.
Manila Shares
- Shared file storage that can be mounted by multiple VM instances.
- Useful for collaborative datasets, class/workshop material, and shared input/output data for distributed workloads.
- Implemented using OpenStack Manila.
Object Store
- S3-compatible object storage based on OpenStack Swift.
- Useful for public data hosting, web application assets, S3-compatible tools, and HTTP-accessible data.
- Available through Horizon and the OpenStack command line interface.
Jetstream2 does not provide a general backup service for user data. Users should keep offsite copies of important data.
File Transfer
Jetstream2 does not use dedicated data transfer nodes. File transfers are performed directly to and from Jetstream2 virtual machine instances or through web-based and managed transfer tools.
Common transfer methods include the Exosphere web shell/web desktop file-transfer interface, SCP/SFTP to a VM with a public IP address, and Globus for larger or managed transfers. The best method depends on file size, whether the VM has a public IP address, and whether the data is being transferred from a local machine, another endpoint, or another digital resource.
| Supported Methods | Data Transfer Node | URL |
|---|---|---|
| GLOBUS | RECOMMENDED | https://www.globus.org/data-transfer | |
| SCP | ||
| SFTP |
Login to Jetstream2 LM
Jetstream2 is primarily accessed through the Exosphere web interface. Users add their ACCESS account in Exosphere and authenticate through CILogon using ACCESS CI credentials. Multi-factor authentication may be required depending on the user’s ACCESS authentication flow.
After logging in and selecting an allocation, users can create and manage virtual machines, choose Large Memory flavors, access web shell or web desktop sessions, manage storage volumes, view instance IP addresses, and configure SSH access for their own VM instances.