Help

Limits

These are the limits as of this version, from the code and the open work around it.

Not built yet#

A default deploy runs the stand-in simulator, cascade worker --replay, unless you pass --base-image, --sim-cmd and --accelsim-dir. Its numbers come from a recorded log, not from your trace.
The profiler doesn't capture real hardware timing (real_timing.json) yet, so the comparison shows simulated time only.
Each sim models one GPU. Making many simulated GPUs act as one system is the next step, not something Cascade does yet.
The Sail launcher is written against the Sail SDK 0.17.2 source and tested with a fake SDK. It hasn't run against the live Sail service.
The S3 endpoint accepts anonymous uploads. Anyone with its URL can add a trace.

Each entry in a run has a count from 1 to 64. A run can have any number of entries.
A trace only runs on configs of the architecture it was captured on.
The app launches up to 8 sims at a time. Larger runs launch in waves.
A subscriber to the event stream can fall up to 2000 events behind before the app disconnects it.
log_tail holds the last 20 lines. The full log is always available as a download.
A sim's output files can be up to 64 MiB each and 256 MiB in all. The app has no way to delete them.

Traces grow with the layers, tokens and forward passes you trace. A small layer is tens of MB. Whole models with long prompts can reach hundreds of GB.
The app needs about 2.2 times the uploaded size in disk, for the raw and processed trace.
Simulation is far slower than real hardware. Start with one layer and a few tokens.
The profiler's Modal function times out after 4 hours.