Skip to content

Commit 93147e5

Browse files
authored
spell fix (#732)
1 parent 3be5ebd commit 93147e5

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/design/modeling-optimization.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ WVA uses modeling, benchmarking, and optimization to find the best possible solu
88

99
## Definitions and assumptions
1010

11-
- An **accelerator** is a unit of allocation of (GPU) devices, of a given type and multiplicity, e.g. 2xH100 is an accelarator consisting of two H100 GPUs, in order to satisfy model memory constraints and/or performance.
11+
- An **accelerator** is a unit of allocation of (GPU) devices, of a given type and multiplicity, e.g. 2xH100 is an accelerator consisting of two H100 GPUs, in order to satisfy model memory constraints and/or performance.
1212

1313
- An **accelerator arrangement** consists of one or more accelerators in parallel (tensor or pipeline parallelism) assigned to a model server.
1414

@@ -41,7 +41,7 @@ The former is used to estimate performance given the current and/or predicted/an
4141

4242
Typically, analytical performance models have their own internal parameters. For example, the base and slope of the linear relationship between ITL and batch size ([explained below in more detail](#deriving-performance-parameters-through-linear-fit)), are parameters of the model. In this case, the determination of such parameters may be achieved through offline benchmarking and/or online through observations and tuning (dynamic adjustment of parameter values to match observations).
4343

44-
The other relevant performance parameter is an upper bound on the batch size, given a particular average number of tokens per request, beyond which preformance degrades severely.
44+
The other relevant performance parameter is an upper bound on the batch size, given a particular average number of tokens per request, beyond which performance degrades severely.
4545

4646
## Benchmarking methodology
4747

0 commit comments

Comments
 (0)