# Overview

## What is GigaSPOT?

**GigaSPOT** is Clore.ai's advanced bidding system for GPU power. Think of it as a "stock market" for computing — you bid on GPU time, and the system automatically finds you the best deals.

### Who is GigaSPOT for?

| User Type        | Use Case                                  |
| ---------------- | ----------------------------------------- |
| **Miners**       | Bid for GPU power at optimal prices       |
| **ML Engineers** | Run batch jobs with flexible pricing      |
| **Power Users**  | Fine-tune GPU settings (OC, power limits) |

### GigaSPOT vs Regular Spot

| Feature | Regular Spot     | GigaSPOT                  |
| ------- | ---------------- | ------------------------- |
| Pricing | Fixed per-server | Bid per GPU power         |
| Control | Basic            | Full OC control           |
| Bidding | Simple outbid    | Smart power-based bidding |

***

## How It Works

GigaSPOT is a trading system for GPU server owners and clients demanding computing power for interruptible tasks. The system is a self-regulated permissionless market where all parties are incentivized to create maximum positive outcome.

GigaSPOT allows anyone to place bids on machines with any workload

<figure><img src="https://2864042869-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbyNlC5NV8aIpXnc76G7w%2Fuploads%2FGBIC0WIv6qCNr9OTucAs%2FCLORE%20Graph%201.png?alt=media&#x26;token=ea727100-3108-4344-be6b-5f001e156f9f" alt=""><figcaption><p>Showcase how GigaSPOT choses the most profitable bid for the host</p></figcaption></figure>

Power is guaranteed by client requesting power limit for GPU(s) in the machine. Let's imagine a workload that is bottlenecked by VRAM bandwith and 450W GPU will end up drawing only 280W. Lowering Power Limit to 280W has no impact on workload speed. Because of this we decided to assume power limit as workload power draw

***

<figure><img src="https://2864042869-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbyNlC5NV8aIpXnc76G7w%2Fuploads%2FdDE4JeHtyBvpDHGU4EiW%2FCLORE%20Graph%202.png?alt=media&#x26;token=07313a8b-42c4-4848-a0d0-0e5f25a4c981" alt=""><figcaption><p>Diagram of workload creation, move between workloads</p></figcaption></figure>

Workloads get reevaluated on each billing interval to determine the most profitable one

***

## Workload Specifics

* Docker image from CCR or predefined image configured by ENV
* Price in $CLORE/day
* Overclocking settings (individual per each GPU in machine)
  * Power Limit (W) \*mandatory
  * Core Lock (MHz)
  * Mem Lock (MHz)
  * Core Offset (MHz)
  * Mem Offset (MHz)
* Environmental Variables \*optional

While it's not mandatory to setup `Core Lock` `Mem Lock` `Core Offset` `Mem Offset` it's very much recommend to achieve expected performance, because otherwise it's values can't be guaranteed

Power Limit can be specified in range of card minimum to PL set by hosting provider in background job OC

Locks and Offsets could be configured in allowed ranges chosen by CLORE.AI team, these ranges are specified in the [snapshot of the marketplace](https://gigaspot-api-docs.clore.ai/get-market-12836589e0)