Jetstream2 Large Memory is a cloud-based computing resource that provides on-demand virtual machines with significantly increased memory capacity for data-intensive applications. It is designed for workloads that require more memory than standard CPU instances but do not necessarily require GPU acceleration.
Large Memory instances are well suited for applications such as in-memory databases, large-scale data analytics, genomics, graph processing, and other workloads that require high RAM capacity. Like other Jetstream2 resources, users have full control over their virtual machine environments, including operating system, software stack, and runtime configuration.
Login to Jetstream2 LM
Jetstream2 is primarily accessed through a web-based portal called Exosphere. Users log in using ACCESS CI credentials via CILogon authentication. Multi-factor authentication is required, and users must have an active Jetstream2 allocation before accessing resources.
After logging in, users can:
Launch virtual machines
Manage storage volumes
View instance IP addresses
Upload SSH keys
File Transfer
Jetstream2 does not use dedicated data transfer nodes. All transfers occur directly between the user’s local machine and the virtual machine.
| Supported Methods | Data Transfer Node | URL |
|---|---|---|
| GLOBUS | RECOMMENDED | https://www.globus.org/data-transfer | |
| SCP | ||
| SFTP |
Storage
File System
| Directory | Path | Quota | Purge | Backup | Notes |
|---|
External Storage
Storage Filesystems
Jetstream2 does not use shared HPC file systems. Storage is attached to virtual machines.
Instance Storage
- Local disk tied to the VM
- Deleted when the instance is deleted
- Used for temporary data and runtime files
Persistent Volumes
- Independent block storage attached to VMs
- Survives instance restarts
- Can be detached and reattached to different instances
- Used for long-term datasets
Typical mount path:
/media/volume/<volume-name>
File Shares
- Shared storage accessible across multiple VMs
- Implemented using OpenStack Manila
- Used for collaboration and shared datasets
Typical mount path:
/media/share/<share-name>
Jobs
Jetstream2 Large Memory does not use a centralized scheduler. Jobs are run directly on virtual machines created by the user.
Users execute workloads interactively or via scripts within the VM environment. For example:
python analysis.pyIf scheduling is required, users can deploy their own tools such as Slurm or Kubernetes within their virtual infrastructure.
Resource usage is based on VM size and runtime rather than queued jobs.
Queue specifications
| Name | Purpose | CPUs | GPUs | RAM | Jobs
30 days
|
Wait Time
30-day trend
|
Wall Time
30-day trend
|
|---|---|---|---|---|---|---|---|
| Indiana Jetstream2 Large Memory | AMD Milan 7713 | 8 GB per CPU Core | — | — | — |