This page explains how HPC resources are allocated, how usage is measured, and how to request additional resources for research projects.
Most users can start working immediately using the default allocation. Larger projects, GPU-intensive workloads, and research collaborations may require additional resources.
Resource allocations define how much of the HPC infrastructure a user or project may consume over time.
Resources are measured as:
A CPU-hour means one CPU core used for one hour.
Examples:
| Resources Used | Consumption |
|---|---|
| 1 CPU for 1 hour | 1 CPU-hour |
| 4 CPUs for 1 hour | 4 CPU-hours |
| 8 CPUs for 2 hours | 16 CPU-hours |
| 1 GPU for 1 hour | 1 GPU-hour |
| 4 GPUs for 2 hours | 8 GPU-hours |
New users receive a default allocation based on their affiliation.
| User Type | CPU Hours / Month | GPU Hours / Month |
|---|---|---|
| VU MIF Users | 2000 | 100 |
| Other Vilnius University Users | 100 | 10 |
| External Users | Project-specific | Project-specific |
<note tip> The default allocation is intended for coursework, learning, testing, and smaller research workloads. </note>
CPU and GPU usage are accumulated for all completed jobs.
Example:
4 CPU cores × 3 hours = 12 CPU-hours
Example:
2 GPUs × 5 hours = 10 GPU-hours
<note> Resource usage is based on allocated resources, not the actual resource utilization of an application.
For example, if a job reserves 8 CPU cores but actively uses only 4, accounting will still charge all 8 allocated CPU cores. </note>
If your jobs stop starting because of:
AssocGrpCPUMinutesLimit
or
AssocGrpGRESMinutes
you may have reached your allocation limit.
Display CPU and GPU usage for the current month:
sreport -T cpu,mem,gres/gpu cluster AccountUtilizationByUser \ Start=$(date +%m01) End=$(date +%m31) User=$USER
<note tip> Resource usage is reported in minutes.
Divide by 60 to obtain hours. </note>
Display allocation information:
sshare -l -A USERNAME_mif -p \ -o GrpTRESRaw,GrpTRESMins,TRESRunMins
Replace USERNAME with your HPC username.
Fields:
| Field | Description |
|---|---|
GrpTRESRaw | Resources already consumed |
GrpTRESMins | Resource limit |
TRESRunMins | Resources currently consumed by running jobs |
Consider requesting additional resources when:
Typical examples:
Additional resources can be requested through the IT Research Center service portal:
IT Research Center (ITRC) Service Requests
When submitting a request, it is helpful to provide:
Providing accurate information helps administrators assign resources more efficiently.
Resource increases are normally granted for the current month and future months.
Example:
Additional allocation granted:
600 - 40 = 560 GPU-hours available
The new monthly limit in future months becomes:
600 GPU-hours/month
Unused resources do not carry over to the next month.
Larger allocations are usually managed through projects.
Project allocations make it possible to:
Jobs submitted under a project allocation use:
#SBATCH --account=alloc_xxxx_project
Example:
#!/bin/bash #SBATCH --account=alloc_xxxx_project #SBATCH --partition=main #SBATCH --cpus-per-task=4 #SBATCH --time=01:00:00 python3 script.py
Project allocations are managed through Waldur.
Waldur provides:
For details see:
Efficient resource usage helps everyone access the cluster more quickly.
Recommended practices:
Avoid:
<note tip> A smaller and more accurate resource request often starts faster than an oversized job. </note>
Check whether you have exceeded your allocation limits.
Common errors include:
AssocGrpCPUMinutesLimit AssocGrpGRESMinutes
These usually indicate that additional resources are required.
Usually not.
Most VU MIF users can work using their default monthly allocation.
Most VU MIF users do not.
Only users working within a project allocation should use:
#SBATCH --account=alloc_xxxx_project
Yes.
Project allocations can be shared between project members.
No.
Allocations are renewed according to the approved monthly limits.
Your CPU allocation has been exhausted.
Check current usage and request additional resources if necessary.
Your GPU allocation has been exhausted.
Check current usage and request additional resources if necessary.
Verify that:
Now that you understand how resources are allocated and managed, continue with:
You may also revisit:
<note> This guide was prepared and updated by the VU MIF HPC team with the assistance of Microsoft Copilot. All procedures and examples should be validated against the current HPC environment, software stack, and operational policies. </note>