- Performance Analysis:
  - There are a number of threads that will always show up:
    main
      This is the main thread run when NeXtMidas is started.
      The performance readings for this thread are usually misleading since they include time spent waiting for user input at the `nM>` shell prompt.
      If your macro is not run with the `/BG` switch its performance will be included along with this thread. (This is why you want to run your command with `/BG` when using the profiler.)
    AWT-EventQueue-0
      This is the thread responsible for graphical rendering of AWT and Swing components.
      This thread also handles events triggered via a GUI interaction (e.g. clicking a button).
      On occasion you may need to look at the performance of this thread since it will include event handling.
    Finalizer, Reference Handler, Signal Dispatcher, Java2D Disposer, AWT-XAWT & AWT-Shutdown
      These threads are internal to the Java VM.
      Most of these threads are special-purpose and spend almost all of their time in "wait" (i.e. they aren't using any CPU time).
      You can ignore these threads.