mirror of
https://github.com/clearml/clearml-docs
synced 2025-06-26 18:17:44 +00:00
Small edits (#455)
This commit is contained in:
@@ -148,7 +148,7 @@ configuration [here](#aws-iam-restricted-access-policy).
|
||||
1. Complete creating the policy
|
||||
1. Attach the created policy to an IAM user/group whose credentials will be used in the autoscaler app (you can create a
|
||||
new IAM user/group for this purpose)
|
||||
1. Obtain a set of AWS IAM credentials for the user/group to which you have attached the created policy in the previous step
|
||||
1. Obtain a set of AWS IAM credentials for the user/group to which you have attached the created policy in the previous step
|
||||
|
||||
|
||||
### AWS IAM Restricted Access Policy
|
||||
|
||||
@@ -6,7 +6,7 @@ title: GCP Autoscaler
|
||||
The ClearML GCP Autoscaler App is available under the ClearML Pro plan
|
||||
:::
|
||||
|
||||
The GCP Autoscaler Application optimizes GCP VM instance usage according to a user defined instance budget: Define your
|
||||
The GCP Autoscaler Application optimizes GCP VM instance usage according to a user defined instance budget: Define your
|
||||
budget by specifying the type and amount of available compute resources.
|
||||
|
||||
Each resource type is associated with a ClearML [queue](../../fundamentals/agents_and_queues.md#what-is-a-queue) whose
|
||||
|
||||
@@ -16,7 +16,7 @@ ClearML provides the following applications:
|
||||
* [**GPU Compute**](apps_gpu_compute.md) - Launch cloud machines on demand and optimize their usage according to a
|
||||
defined budget--no previous setup necessary
|
||||
* [**AWS Autoscaler**](apps_aws_autoscaler.md) - Optimize AWS EC2 instance usage according to a defined instance budget
|
||||
* [**GCP Autoscaler**](apps_gcp_autoscaler.md) - Optimize GCP instance usage according to a defined instance budget
|
||||
* [**GCP Autoscaler**](apps_gcp_autoscaler.md) - Optimize GCP instance usage according to a defined instance budget
|
||||
* [**Hyperparameter Optimization**](apps_hpo.md) - Find the parameter values that yield the best performing models
|
||||
* **Nvidia Clara** - Train models using Nvidia’s Clara framework
|
||||
* [**Project Dashboard**](apps_dashboard.md) - High-level project monitoring with Slack alerts
|
||||
|
||||
@@ -132,7 +132,7 @@ The following table describes the actions that can be done from the experiments
|
||||
that allow each operation.
|
||||
|
||||
Access these actions with the context menu in any of the following ways:
|
||||
* In the experiments table, right-click an experiment or hover over an experiment and click <img src="/docs/latest/icons/ico-dots-v-menu.svg" alt="Dot menu" className="icon size-md space-sm" />
|
||||
* In the experiments table, right-click an experiment or hover over an experiment and click <img src="/docs/latest/icons/ico-dots-v-menu.svg" alt="Dot menu" className="icon size-md space-sm" />
|
||||
* In an experiment info panel, click the menu button <img src="/docs/latest/icons/ico-bars-menu.svg" alt="Bar menu" className="icon size-md space-sm" />
|
||||
|
||||
| Action | Description | States Valid for the Action | State Transition |
|
||||
|
||||
@@ -6,7 +6,7 @@ Use the Projects Page for project navigation and management.
|
||||
|
||||
Your projects are displayed like folders: click a folder to access its contents. The Projects Page shows the top-level
|
||||
projects in your workspace. Projects that contain nested subprojects are identified by an extra nested project tab.
|
||||
An exception is the **All Experiments** folder, which shows all projects’ and subprojects’ contents in a single, flat
|
||||
An exception is the **All Experiments** folder, which shows all projects’ and subprojects’ contents in a single, flat
|
||||
list.
|
||||
|
||||

|
||||
|
||||
@@ -24,7 +24,7 @@ The worker table shows the currently available workers and their current executi
|
||||
|
||||
|
||||
Clicking on a worker will open the worker’s details panel and replace the graph with that worker’s resource utilization
|
||||
information. The resource metric being monitored can be selected through the menu at the graph’s top left corner:
|
||||
information. The resource metric being monitored can be selected through the menu at the graph’s top left corner:
|
||||
* CPU and GPU Usage
|
||||
* Memory Usage
|
||||
* Video Memory Usage
|
||||
@@ -37,7 +37,7 @@ The worker’s details panel includes the following two tabs:
|
||||
* Current Experiment - The experiment currently being executed by the worker
|
||||
* Experiment Runtime - How long the currently executing experiment has been running
|
||||
* Experiment iteration - The last reported training iteration for the experiment
|
||||
* **QUEUES** - information about the queues that the worker is assigned to:
|
||||
* **QUEUES** - Information about the queues that the worker is assigned to:
|
||||
* Queue - The name of the Queue
|
||||
* Next experiment - The next experiment available in this queue
|
||||
* In Queue - The number of experiments currently enqueued
|
||||
|
||||
Reference in New Issue
Block a user