# Run in the Cloud Environment

{% hint style="info" %}
**Each cloud run can be configured differently.**
{% endhint %}

**STEP 1.**

Don't waste cloud resources! Run some local tests first.

If a code doesn't run on your environment, it won't run on the cloud. 

<figure><img src="/files/wsduzmvJvyuLbph0YP9R" alt=""><figcaption><p>Local test</p></figcaption></figure>

**STEP 2.**

The system is parsing your code dependencies to assign you a CPU or GPU cloud environment.

{% hint style="info" %}
GPUs are very expensive and bad for the environment. 🌳

Don't claim a GPU if you don't need it!
{% endhint %}

<figure><img src="/files/LmRKCXiIKBUsrRo1lpQO" alt=""><figcaption><p>GPU vs CPU</p></figcaption></figure>

**STEP 3.**

You can configure the re-training frequency of your model as you wish.

{% hint style="info" %}
Remember that your code will need to process all the dates in the private test set in under 5 hours of compute. Adjust your retraining frequency so that your code remains within the limits.
{% endhint %}

<figure><img src="/files/k3lK9mDpF4W7LSXi2mMB" alt=""><figcaption><p>Training frequency</p></figcaption></figure>


---

# 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.adialab.crunchdao.com/participate/run-in-the-cloud-environment.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.