Tracking usage

The web app includes a usage tracking page.

The chart shows how many core-hours you’ve used this calendar month, and distinguishes between hours used for testing and debugging.

What’s a core-hour?

A core-hour is a CPU-hour of work in Antithesis. Antithesis runs all tasks in massive parallel, so you can expect a wall-clock hour of testing to consume many core-hours, generally 48 or more. The advantage of this is that you get over a full day (or 2, or 4) of testing time in a single wall-clock hour.

What counts towards my usage?

The following activities consume core-hours:

Running a test

Running a test consumes a variable number of core-hours per wall-clock hour, based on the performance tier chosen.

Higher performance tiers increase parallelism to explore your system’s state space faster, and consume more core-hours per wall-clock hour.

You can cancel a test at any time after starting.

The time required to initialize the system under test counts towards usage. You can minimize this overhead by keeping your system’s services and initialization streamlined.

Each test run requires a small amount of setup time, which does count toward usage.

Running a causality analysis

Running a causality analysis consumes 48-core hours per wall-clock hour by default.

Each causality analysis requires a small amount of setup time to rewind to the moment of interest, which does count toward usage.

Using multiverse debugging

Multiverse debugging sessions consume 48-core hours per wall-clock hour.

Multiverse debugging sessions last 6 wall-clock hours by default, and users can cancel the session once they’re done.

Each multiverse debugging session requires a small amount of setup time to rewind to the moment of interest, which does count toward usage.