Compute

Compute is used for the following functions in Decthings:

• Evaluate

• Train

• Create state

• Debug sessions

• Terminal sessions

• Spawned commands

• Persistent launchers

There are three separate costs that apply when you run these operations. These are per-operation pricing (a fixed price for each operation), launcher princing (cost for compute resources such as CPU and memory), and input/output data pricing.

Per-operation pricing

For Evaluate, Train, Create state, Debug sessions, Terminal sessions and Spawned commands, a small cost is applied each time you execute one of these operations in the cloud. For operations that you run on your own device (for example by using tools that download your model and run it locally), there is no per-operation cost applied.

Note: For debug sessions, the cost is applied when starting the session, as well as for each operation executed within the debug session (create state, evaluate and train)

Cost for operations executed in the cloud: $0.0001 per operation

Launcher pricing

With Decthings, compute workloads that you request to run in the cloud are executed inside isolated virtual machines, in Decthings called launchers.

By choosing the right launcher size you can reduce your monthly bill. For simple models that don't require much processing power, you can go as low as 128 MiB memory and 1/8th CPU core (the rest of the core is shared with other users).

Launchers can either be persistent or temporary. A temporary launcher will be discarded when the operation is complete. A persistent launcher will be kept alive and ready even if there are no operations running on it. You are billed for a persistent launcher even if there is nothing running on it. If there are multiple simultaneous operations running on a single persistent launcher, you are still only billed for the single persistent launcher.

• The same billing model and prices apply to both temporary and persistent launchers.




• A launcher is priced separately for its CPU, memory and disk. When configuring which launcher to use, you can specify precisely how much of each of these three resource types you need.




• Before the price is calculated, the duration that a launcher is used is rounded up to the next whole second. The minimum amount of time billed for a single launcher is 1 second.




• The first hour that a launcher is running is called the warmup period. After the warmup period ends, a discounted price will be applied. For persistent launchers, if the launcher for any reason crashes and is restarted, the warmup period is not reset. That is, you will not have to pay for warmup multiple times. If you remove the persistent launcher and create it again then the warmup period is reset.




• In addition to launcher usage, there are other costs that apply for operations. These are listed in 'Operation pricing'.




• If you run many operations, consider using a persistent launcher. In addition to improved response times due to reduced launcher startup and model initialization times, the total cost can become lower for a single persistent launcher than many temporary ones running for the same amount of time (because of the discount after the warmup period).

The following costs apply for launchers, regardless of launcher type (temporary or persistent) or operation type (evaluation, training session, etc).

Input/output data pricing

An additional cost is applied for the amount of input and output data sent to and from functions. This cost applies to functions that take input data and/or return output data (Evaluate, Train and Create state) as well as the input/output (stdin, stdout and stderr) of Terminal sessions, Spawned commands and Debug sessions. The cost is also applied to the input/output data of operations that you execute inside the debug sessions, for example evaluate.

For Create state (and Get state inside debug sessions), the cost is not applied to the created state. This is because the created state is stored within Decthings servers, not sent as output data.

The cost is also not applied for operations that you run on your own device.

Input data cost for operations running in the cloud: $0.3 per GiB
Output data cost for operations running in the cloud: $0.3 per GiB

Models

Models are billed for their:

• Filesystem size

• States size

• Snapshots filesystem sizes and states sizes

Operations such as evaluations, training sessions, etc. are covered in the Compute section.

Filesystems

The model filesystem contains code and other data required to run the model. The filesystem size does not depend on the actual data stored, but only on which filesystem size you have selected. You cannot accidentally exceed the filesystem size and be billed higher than expected, since any request to write data over the limit will fail.

The price is displayed in USD per gibibyte-month (1024^3 bytes for 730 hours). The total filesystem size used is accumulated over the month and takes into account changes to the size. For example, if you use a filesystem of 1 GiB for one half month, and then upgrade to 3 GiB for the second half of the month, the total used filesystem size will be 2 GiB-months (1 * 0.5 + 3 * 0.5).

Models that are based on the snapshot of another models will not be priced for their filesystem nor their snapshot's filesystems. This is because in this case, the same filesystem as the original snapshot is used. The prices for filesystems only apply for models that are not based on the snapshot of another model.

Filesystem cost: $0.5 per GiB-month

States

The following price is applied for each of the model's states, as well as the states of each of the model's snapshots.

The price is displayed in USD per gibibyte-month (1024^3 bytes for 730 hours). The total states size used is accumulated over the month and takes into account changes to the size. For example, if you store 1 GiB for one half month, and 3 GiB for the second half of the month, the total used states size will be 2 GiB-months (1 * 0.5 + 3 * 0.5).

State cost: $0.3 per GiB-month

Snapshots

When snapshotting a model, the files are copied into a new filesystem with the same size as the model's filesystem, and the model's current state is copied into the snapshot. You are billed for this new filesystem, and for this new state, at the same price as for the original model. That is, the total billed filesystem size for a model is the model filesystem size plus the sum of all the snapshots filesystem sizes, and the total billed states size for a model is the sum of all model states size plus the sum of all the snapshots state sizes. If you change the filesystem size of the model, or update the model state, the snapshots will be unaffected.

Datasets

Datasets are billed for the total size of the stored data.

The price for data storage is displayed in USD per gibibyte-month (1024^3 bytes for 730 hours). The billed amount is accumulated over the month. For example, if you store 1 GiB for one half month, and 3 GiB for the second half of the month, you will be billed for one GiB-month (1 * 0.5 + 3 * 0.5).

Dataset storage cost: $0.3 per GiB-month