Skip to content
This repository was archived by the owner on Aug 15, 2019. It is now read-only.

Commit 4d54e63

Browse files
nbardyNikhil Thorat
authored andcommitted
Update to reflect new DEBUG mode API (#896)
1 parent 191d4da commit 4d54e63

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/tutorials/performance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -135,12 +135,12 @@ memory will get cleaned up automatically by the JavaScript garbage collector.
135135
## Debug mode
136136

137137
Another way to monitor your application is by calling
138-
`NDArrayMath.enableDebugMode()`. In debug mode, we will profile every
139-
`NDArrayMath` function that gets called while the application is running,
138+
`dl.ENV.set('DEBUG',true)`. In debug mode, we will profile every
139+
`Tensor` function that gets called while the application is running,
140140
logging the command, the wall time in milliseconds, the rank, shape and the
141141
size. We also will check the activations for NaNs and throw an exception as soon as a NaN is introduced.
142142

143-
![NDArrayMath.enableDebugMode](debugmode.png "NDArrayMath.enableDebugMode")
143+
![DEBUG](debugmode.png "DEBUG")
144144

145145
This can give you a sense for which operations are the bottleneck in
146146
your application, and which activations are using large amounts of memory.

0 commit comments

Comments
 (0)