KyRIC is a large-memory cluster operated by the University of Kentucky's Center for Computational Sciences. It has five large-memory compute nodes, each with 3 TB of RAM and a 5 TB local SSD array. The shared memory and local SSD space suit memory-intensive analysis of big data, including genome sequencing, processing of large text corpora, and graph analytics. KyRIC is for single-node jobs only; multi-node jobs, such as those using MPI, are not recommended.
Jobs
KyRIC allocations are made in core-hours. The recommended method for estimating your resource needs for an allocation request is to perform benchmark runs.
KyRIC core-hour calculations should assume that all jobs will run in the normal partition and that they are charged for all 40 cores for the wall-clock time the node is held; if the job exits early, the node is released and charging stops.
Example job scripts can be found in the user manual.
*core-hours are cores x wall-clock hours
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
|
|---|---|---|---|---|---|---|---|---|
| normal | Production single-node batch jobs | 5 | Intel Xeon E7-4820 v4 (40 cores) | — | 3 TB | — | — | — |
Storage
No tier is backed up; users are responsible for their own backups.
File System
| Directory | Path | Quota | Purge | Backup | Notes |
|---|---|---|---|---|---|
| Home | $HOME | 10 GB | Scripts and configuration only - not for datasets. | ||
| Project | $PROJECT | 500 GB | Shared group data. | ||
| Scratch | $SCRATCH | 10 TB | 30-day | Main working area. | |
| Compute Node Local | 5 TB | Wiped at job end | Per-node SSD scratch, deleted at job end. |
External Storage
The five dedicated ACCESS nodes have exclusive access to approximately 300 TB of network attached disk storage, reachable through the compute nodes during job execution.
File Transfer
KyRIC supports SCP, RSYNC, and Globus file transfers. They recommend to transfer data through the high-speed data transfer node (DTN) and not through the login nodes. SCP and RSYNC can only be used if you have your ssh keys setup. If you are unfamiliar with Globus, see the transfer tutorial. How To Log In and Transfer Files with Globus.
| Supported Methods | Data Transfer Node | URL |
|---|---|---|
| GLOBUS | RECOMMENDED | Globus | |
| SCP | RECOMMENDED | kxc-dtn.ccs.uky.edu | KXC Cluster |
| RSYNC | RECOMMENDED | kxc-dtn.ccs.uky.edu | KXC Cluster |
Login to KYRIC
Kyric supports access through both SSH keys and web GUI at kxc-ood.ccs.uky.edu.
For SSH, a user must generate and install their own keys. To register your key with KyRIC, log into SSH Key Management System to submit a new one or follow the operator's Requesting login to ACCESS KyRIC cluster guide.
Once your key is installed, connect:
$ ssh -i id_rsa username@kxc.ccs.uky.edu
*id_rsa is the name of your private key
SSH Login
$ ssh <your_username>@kxc.ccs.uky.edu