Skip to content

Commit bc25d34

Browse files
Youssef1313mairaw
authored andcommitted
Use dotnetcli in DiagnosticScenarios/readme.md (#1855)
* Fix link in DiagnosticScenarios/readme.md * Update readme.md * Update readme.md
1 parent 2211655 commit bc25d34

File tree

1 file changed

+13
-5
lines changed
  • core/diagnostics/DiagnosticScenarios

1 file changed

+13
-5
lines changed

core/diagnostics/DiagnosticScenarios/readme.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The sample debug target is a simple `webapi` application. The sample triggers un
1616

1717
After downloading the source, you can easily run the webapi using:
1818

19-
```console
19+
```dotnetcli
2020
dotnet build
2121
dotnet run
2222
```
@@ -27,24 +27,32 @@ The target triggers undesirable behaviors when hitting specific URLs.
2727

2828
### Deadlock
2929

30-
`http://localhost:5000/api/diagscenario/deadlock`
30+
```http
31+
http://localhost:5000/api/diagscenario/deadlock
32+
```
3133

3234
This method will cause the target to hang and accumulate many threads.
3335

3436
### High CPU usage
3537

36-
`http://localhost:5000/api/diagscenario/highcpu/{milliseconds}`
38+
```http
39+
http://localhost:5000/api/diagscenario/highcpu/{milliseconds}
40+
```
3741

3842
The method will cause to target to heavily use the CPU for a duration specified by {milliseconds}.
3943

4044
### Memory leak
4145

42-
`http://localhost:5000/api/diagscenario/memleak/{kb}`
46+
```http
47+
http://localhost:5000/api/diagscenario/memleak/{kb}
48+
```
4349

4450
This method will cause the target to leak memory (amount specified by {kb}).
4551

4652
### Memory usage spike
4753

48-
`http://localhost:5000/api/diagscenario/memspike/{seconds}`
54+
```http
55+
http://localhost:5000/api/diagscenario/memspike/{seconds}
56+
```
4957

5058
This method will cause intermittent memory spikes over the specified number of seconds. Memory will go from base line to spike and back to baseline several times.

0 commit comments

Comments
 (0)