Stunner - Profiling for Stunner / Lienzo

The mail goal for this task is to identify potential bugs (such as memory leaks) and the (potential) areas to be improved as well. The result of this task should end up on different (new) tickets and tasks candidates for being implemented during the execution phase.

Some of the behaviours (in terms of non properly responsive experience) to profile and consider improving, as from field & users' feedback are:

• The tool loading/rendering times
• The response times when performing node selection
  • consider first times selection vs cached data
  • consider multiple selection
• The response times while dragging nodes (shapes) around (consider multiple)
• The performance degradation on large models / canvas

Also some indicators worth to be checked:

• Memory usage (JS Heap)
• Check memory leaks
• Event Listeners usage
• Instance (node) creation
• Animation frames - duration & idle times, fps rate
• Degradation on each "active/paused" process editor instance
• Code usage vs dead code (chrome devtools)
• Performance on MAC

Also this document describes some analysis and finding for initial profiling actions:
https://docs.google.com/document/d/1fnBWesk3esequngxU08GOTbrVXX4cRUq_oo59Krnh9Y/edit?usp=sharing

Acceptance criteria

The document containing analyses for all points mentioned above is created.