| Total users | 4 |
|---|---|
| Total projects | 6 |
| Total data under management | 0.003 KB |
| Total storage usage | 0.003 KB |
| Deduplication ratio | 1.0 |
| Approximate monthly storage cost | $0.00 |
See note on usage and cost calculations for details on how costs are calculated.
| Active users | 1 |
|---|---|
| Active projects | 1 |
| Workflow runs | 1 |
| Compute used | 1.5 hours |
| Compute cost | $0.23 |
| Storage cost | $0.00 |
See note on usage and cost calculations for details on how costs are calculated.
| Project | Users | Active | Compute usage (hours) | Compute cost |
|---|---|---|---|---|
| WGS chr19 test for 2.7.2~rc3 | User1 | 2024-04-05 to 2024-08-22 | 1.5 | $0.23 |
See note on usage and cost calculations for details on how costs are calculated.
| Users | Active | Compute usage (hours) | Compute cost |
|---|---|---|---|
| User1 | 2024-04-05 to 2024-08-22 | 1.5 | $0.23 |
| Workflow run count | Workflow name | Median runtime | Mean runtime | Median cost per run | Mean cost per run | Sum cost over runs |
|---|---|---|---|---|---|---|
| 1 | WGS processing workflow scattered over samples (v1.1-2-gcf002b3) | 1:19:21 | 1:19:21 | $1.37 | $1.37 | $1.37 |
The numbers presented in this report are estimates and will not perfectly match your cloud bill. Nevertheless this report should be useful for identifying your main cost drivers.
"Total data under management" is what you get if you add up all blocks referenced by all collections in Workbench, without considering deduplication.
"Total storage usage" is the actual underlying storage usage, accounting for data deduplication.
Storage costs are based on AWS "S3 Standard" described on the Amazon S3 pricing page:
Finally, this only the base storage cost, and does not include any fees associated with S3 API usage. However, there are generally no ingress/egress fees if your Arvados instance and S3 bucket are in the same region, which is the normal recommended configuration.
"Compute usage" are instance-hours used in running workflows. Because multiple steps may run in parallel on multiple instances, a workflow that completes in four hours but runs parallel steps on five instances, would be reported as using 20 instance hours.
"Runtime" is the actual wall clock time that it took to complete a workflow. This does not include time spent in the queue for the workflow itself, but does include queuing time of individual workflow steps.
Computational costs are derived from Arvados cost calculations of container runs. For on-demand instances, this uses the prices from the InstanceTypes section of the Arvado config file, set by the system administrator. For spot instances, this uses current spot prices retrieved on the fly the AWS API.
Be aware that the cost calculations are only for the time the container is running and only do not take into account the overhead of launching instances or idle time between scheduled tasks or prior to automatic shutdown.