# Application resources

### Size and price of an application

Application sizes can be changed at any time during the lifetime of a project, as long as it is in an active state. Running applications need to be restarted after size change for changes to take effect.

You can read more about the accounting aspect of application sizes in the [pricing structure](/pricing-and-billing/pricing-structure.md#application-resource-accounting).

{% hint style="info" %}
Note that application size refers to the **compute resources** (CPU, RAM, GPU, etc.) of an application. Each application also has a space usage column, which shows how much space the **application files** are using. Space usage comes from any installed packages (conda packages, R packages, database files, etc.)
{% endhint %}

The applications overview shows you a list of the different applications you have added previously, including their configuration version. It also shows their size, which is expressed in compute units for sizes included in your plan, and is expressed in other relevant data for credit-based sizes (e.g., for GPUs the model is indicated).

To view detailed specifications - such as exact CPU and RAM limits - simply hover over the size indicator next to the application.

By default, your applications will be configured to sizes included in the plan provided by your Nuvolos subscription, based on your annual contract with us. Because Nuvolos allows flexible scaling according to your project needs, however, you can always use resources beyond the base ones provided by your subscription. These are paid for in Credits. The "Credit/hour" overview will show whether a given application will consume Credits to run, and if so, how many. For more information on Credits, refer to our documentation on the [Nuvolos pricing structure](/pricing-and-billing/pricing-structure.md#credits).

{% hint style="info" %}
Since credit-based sizes allow Instance Editors to spend credits in the associated resource pool, they need to be [enabled](/administration/space-management/hpc-spaces.md#enable-credit-based-application-sizes) in every space by a space administrator.
{% endhint %}

### Changing application resources

To resize an application:

1. Navigate to the space containing the instance where you want to configure the application.
2. Navigate to the instance containing the application.
3. Make sure you are in the **Current state**.
4. On the sidebar click the Screen button (**Applications**), which shows you the Application list.
5. On the row of the application of interest, hover on the **Size** column where the current application size is shown. Clicking on the icon there takes you to the sizing screen.

The sizing view has two tabs - **INCLUDED** and **CREDIT**.

1. **INCLUDED** sizes consume CUs (compute units).
2. **CREDIT** sizes consume credits.

To change the size, select one of the configurations and click **SET**. After a few seconds, you will be automatically returned to the applications overview.

In order to assist you with selecting the desired resources, the radio buttons at the top left allow you to optimize for CPU, GPU, or storage, depending on what resource your project most needs at the time. This will provide you with different configurations to choose from.<br>

## FAQ

<details>

<summary>Can I change the size of my application while it is running?</summary>

You can change the size of the application any time, however the effect of the change only takes place upon application start. You cannot modify a running workload on the fly.

</details>

<details>

<summary>My GPU application takes time to start - why?</summary>

It is normal that **CREDIT** based dedicated workloads take longer to start - this is due to the fact that resources first need to be checked out for you from the cloud and only then the regular setup process can start. This can take up to 5 to 15 minutes.

In course settings, we suggest [scheduling these workloads for startup](/user-guides/education-guides/configuring-student-applications.md#scheduled-startup-of-student-applications).

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nuvolos.com/features/applications/application-resources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.