File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed
docs/docs/codeflash-concepts Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff 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 :
1313To measure runtime, Codeflash runs a function multiple times with several inputs
1414and 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
1919loops = 0
@@ -31,7 +31,7 @@ number_of_runs = loops
3131
3232The 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
You can’t perform that action at this time.
0 commit comments