Dependencies

• LibAsync
• LibCustomMenu

The Profiler
You have a new tab in your "Journal", now.
There is a button at the bottom to start/stop the profiler.
You get a summary with the functions called and their total time used.
You can click a row to see its call-stack. The shown call-stack is the slowest run to give you a hint what to look for.
For more details there is an "Export" button in the top-right corner. The UI will reload afterwards to save the data to disk.

The profiler auto-starts on reloadui to see what's going on during load. Because settings are not available at that time, this can not be made optional. Load the addon if you want to profile, only.
There is a button to profile the UI during re-load. It enables auto-start profiling and reloads UI. 2 seconds after loading you auto return to the profiler UI.

ESOProfiler Viewer
The addon also includes an external application which allows you to view the exported data with catapult-tracing (used by chrome dev tools for profiling).
In order to use it you need to download node-webkit (note: it's currently not working with the latest version, so make sure to use an older one like v0.33.4) and unzip all files into the viewer folder in the addon. Once done the folder should look like this:

The viewer is started via nw.exe and will automatically load the ESOProfiler.lua from your saved variables folder.
With the save button you can store a trace in catapult-tracing's own json format (you could also just copy ESOProfiler.lua for later use since it is smaller than the resulting json).
The load button allows you to select either a lua or json file which will then be imported for viewing.

The "?" button in the top right shows the navigation help. Most important to know is that alt-mousewheel zooms, click selects an event and drag allows to pan the view.

Warning:
If you capture traces over multiple minutes, the resulting file will become very large and opening it will consume multiple gigabytes of ram. In case the viewer crashes while loading the file you can try to increase the allowed heap size. Just change the value "--max-old-space-size=4096" in package.json from 4096 (MB) to a higher one, but be warned that it can consume all your memory and slow down or crash your system!