FYI, It works with 1.6.0, the output json file was too large for chrome to handle and it silently failed. I reduced the number of iterations to profile to create a smaller file, anything above 500 MB seems to fail. Thanks Sheng for the pointer and Anirudh for the help.
On Thu, May 28, 2020 at 1:07 PM Pedro Larroy <pedro.larroy.li...@gmail.com> wrote: > Yes the profiler seems to be broken / has some concurrency issues. I have > seen corrupted profile results. > > On Thu, May 28, 2020 at 12:30 PM Naveen Swamy <mnnav...@gmail.com> wrote: > > > I am attempting to profile one of our models, I used the profiler.state > to > > run/stop in code and also used the environment variables to autostart the > > profiler. It creates a 600MB json file, however when I view in chrome > > tracing it comes out to be blank screen (loading seems to be fine, didn't > > get any errors) > > > > Wondering if anyone has recently tried or if aware of profiler being > > broken? > > > > ENVIRON: Ubuntu 18.04 > > MXNet : mxnet-cu101mkl > > Deep Learning AMI (Ubuntu 18.04) Version 29.0 (ami-043f9aeaf108ebc37) > > > > Thanks, Naveen > > >
