Jetstream2 Large Memory, also called Jetstream2 LM, provides on-demand high-memory virtual machines for data-intensive workloads that need more RAM than standard CPU flavors.
Official Large Memory flavors include r3.large with 64 vCPUs and 500 GB RAM, and r3.xl with 128 vCPUs and 1000 GB RAM. These flavors are suitable for high-RAM analytics, genomics, graph processing, in-memory databases, and other memory-intensive research applications.
Jobs
Jetstream2 Large Memory is a cloud virtual-machine resource, not a centrally scheduled Slurm cluster. Standard Jetstream2 Large Memory use therefore has no shared login node, Slurm queue, partition, sbatch, srun, or squeue workflow. Slurm commands apply only if a project separately deploys and administers its own virtual cluster.
Users select an r3.large or r3.xl flavor in Exosphere, create a VM, and connect through Web Shell, Web Desktop, or SSH. Only r3.* flavors should be used on the Jetstream2 Large Memory resource.
Applications run directly inside the VM. Users can verify the available memory with free -h, inspect CPU and NUMA information with lscpu and numactl --hardware when available, and run the application directly, for example python large_memory_analysis.py. Software may be installed inside the VM using the operating system package manager, Python environments, containers, or the Jetstream2 software collection.
An active Large Memory instance consumes service units even when no application is running. Users should shelve an instance when it will not be used; a shelved instance consumes zero compute SUs.
See the Jetstream2 Large Memory flavor sizes, RAM, and hourly SU costs, instructions for installing and running software on a Jetstream2 VM, and instructions for shelving and managing an instance to conserve SUs.
Queue specifications
| Name | Purpose | Nodes | CPU cores / node | GPUs / node | Node 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 | 32 | AMD Milan 7713 (128 cores) | — | 1024 GB | — | — | — |
Storage
Jetstream2 provides cloud storage associated with virtual machine instances rather than a traditional shared HPC filesystem. Instances may use ephemeral or volume-backed root disks. Data on an ephemeral root disk is permanently removed when the instance is deleted; retention of a volume-backed root disk depends on the instance's delete-volume setting.
Persistent storage options include block volumes, OpenStack Manila file shares, and S3-compatible object storage. Volumes can be attached to one instance at a time, Manila shares can be mounted by multiple instances, and object storage can be accessed through S3-compatible tools or HTTP. All Jetstream2 allocations receive 1 TB (1000 GB) of storage quota by default; additional storage can be requested through the Indiana Jetstream2 Storage resource.
File Transfer
Jetstream2 does not use dedicated data transfer nodes. Files are transferred directly to and from VM instances or through web-based and managed transfer tools.
Common 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. See the Jetstream2 File Transfer documentation for current guidance.
| Supported Methods | Data Transfer Node | URL |
|---|---|---|
| GLOBUS | RECOMMENDED | https://www.globus.org/data-transfer | |
| SCP | ||
| SFTP |
Login to Jetstream2 LM
2FA/MFA required for login
Jetstream2 Large Memory is accessed primarily through the Exosphere web interface. Users do not create a separate Jetstream2-specific user account. They need an ACCESS account and must be the PI of, or be added to, an active allocation that includes Indiana Jetstream2 Large Memory. Access to Jetstream2 CPU does not automatically provide access to the Large Memory resource.
In Exosphere, select Add allocation, choose Add ACCESS Account, select ACCESS CI (XSEDE) as the CILogon identity provider, sign in with ACCESS credentials, and select the allocation containing the Large Memory resource. ACCESS uses Duo for multi-factor authentication. Users who need to enroll in Duo or manage their authentication devices should follow the ACCESS Duo MFA instructions.
Jetstream2 does not provide a shared SSH login node. Users must first create a Large Memory virtual machine in Exosphere. To create an SSH key pair on a local Linux, macOS, or Windows OpenSSH system, run ssh-keygen -o -a 100 -t ed25519 -C "descriptive-label" -f ~/.ssh/id_ed25519. During instance creation, open the advanced options and select or upload the generated public key, normally ~/.ssh/id_ed25519.pub. Only the public key should be uploaded; the private key must not be shared.
Assign the instance a public IP address when direct SSH access is required. Exosphere-created instances use the exouser account. Connect with ssh -i ~/.ssh/id_ed25519 exouser@<PUBLIC_IP>. Users may alternatively connect through Exosphere Web Shell or Web Desktop.