You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build on top of #1092
### change scopes
- [x] verify api for continuation proofs
- [x] exclude init tables on shard > 0
- [x] ceno-cli with multiple proofs
- [x] separate fixed commitment into 2 set, one for first shard, the
other for non-first shards
- [x] multi-shards ci integration test
### design rationales
`prover_id` and `num_provers` are exposed as CLI arguments to specify
the number of physical provers in a cluster, each mark with a prover_id.
The overall trace data is divided into `shards`, which are distributed
evenly among the provers. The number of shards are in general agnostic
to number of provers. Each prover is assigned `n` shard where n can be
even empty
Shard distribution follows a balanced allocation strategy — for example,
if there are 10 shards and 3 provers, the shard counts will be
distributed as 4, 3, and 3, ensuring an even workload across all
provers.
---------
Co-authored-by: xkx <[email protected]>
0 commit comments