Skip to content

Commit e0f4532

Browse files
committed
minor
1 parent 6775bf5 commit e0f4532

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/docs/codeflash-concepts/benchmarking.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ sidebar_position: 2
44

55
# How Codeflash measures code runtime
66

7-
Codeflash reports benchmarking results that look like this :
7+
Codeflash reports benchmarking results that look like this:
88

99
```text
1010
⏱️ Runtime : 32.8 microseconds → 29.2 microseconds (best of 315 runs)
@@ -13,7 +13,7 @@ Codeflash reports benchmarking results that look like this :
1313
To measure runtime, Codeflash runs a function multiple times with several inputs
1414
and sums the minimum time for each input to get the total runtime.
1515

16-
A simplified pseudocode of Codeflash benchmarking looks like this -
16+
A simplified pseudocode of Codeflash benchmarking looks like this:
1717

1818
```python
1919
loops = 0
@@ -31,7 +31,7 @@ number_of_runs = loops
3131

3232
The above code runs the function multiple times on different inputs and uses the minimum time for each input.
3333

34-
In this document we explain :
34+
In this document we explain:
3535
- How we measure the runtime of code
3636
- How we determine if an optimization is actually faster
3737
- Why we measure the timing as best of N runs

0 commit comments

Comments
 (0)