Developers should have a visualization that can show information from the backend-profiling.

[wdanilo]

This task is automatically imported from the old Task Issue Board and it was originally created by Michael Mauderer.
Original issue is here.

---

Why

We added new capabilities to the profiling framework that integrates some information collected from the engine / language server. To make this information useful, we need to show it together with the GUI profiling information in a way that makes it easy to spot what is happening.

As an IDE developer / project manager / team lead
I want to see what is happening in the engine
So that I can gain insights about performance characteristics of the product.

Acceptance Criteria

This defines what you will walk through to make sure that the story is completed. Developers working on the story should also walk through the acceptance criteria before delivering. The acceptance criteria should be written in the Gherkin language. The Gherkin language was originally created for Cucumber, a Ruby testing suite, and is meant to “enforce firm, unambiguous requirements…and a script for automated testing.” Keep in mind that good feature stories should not, however, be prescriptive in implementation details. The syntax is as follows: GIVEN [necessary context] WHEN [action] THEN [reaction]. Sometimes it helps to walk backwards to determine your GIVEN. If you find yourself writing multiple “and”s in the acceptance criteria, that is a smell test that indicates you should split the story into two or more. Use the following template:

Scenario: 
GIVEN data collected with the new back-end integration. 
WHEN I view the data in our profiling visualisation. 
THEN I can easily see the communication events from the backend. 

Comments:

Michael Mauderer reports a new STANDUP for today (2022-04-19):

Progress: : Updated and merged PR #3382 , updated PR #3388, very quickly created PR #3406 (rust update). Reviewed #3395, and started on building up the functionality to integrate the new data in our Enso based visualisation. It should be finished by 2022-04-21.

Next Day: Next day I will be working on the #same task. Finish the visualisation for the data from #3395. Check&prepare for performance meeting. (Enso Bot - Apr 19, 2022)

---

**Michael Mauderer** reports a new **STANDUP** for yesterday (2022-04-20):

Progress: Worked on some review feedback on the EnsoGL data PR. Continued work on the Multi-Process visualisation. It should be finished by 2022-04-21.

Next Day: Next day I will be working on the #same task. Finish preliminary work on Multi-process PR and open draft PR (which will stay draft until the main Multi-process PR is merged) (Enso Bot - Apr 21, 2022)

---

**Michael Mauderer** reports a new **🔴 DELAY** for today (2022-04-21):

Summary: There is 4 days delay in implementation of the Developers should have a visualization that can show information from the backend-profiling. (#181930315) task.
It will cause 0 days delay for the delivery of this weekly plan.

Actually 1 day delay + weekend + day off.

Delay Cause: Some architectural issue related to setting up dynamic GUI sub-components with FRP attached to parent just took more time than expected. (Enso Bot - Apr 21, 2022)

---

**Michael Mauderer** reports a new **STANDUP** for today (2022-04-21):

Progress: Worked on the visualisation for Multi-process profiling data. Have an almost working prototype, but need to finish some functionality related to hovering over labels and layouting with the rest of the visualisation. That should be finished the next day (Monday) It should be finished by 2022-04-25.

Next Day: Next day I will be working on the #same task. Finish work on multi-process PR and open draft PR (which will stay draft until the main Multi-process PR is merged) (Enso Bot - Apr 21, 2022)

---

**Michael Mauderer** reports a new **🔴 DELAY** for yesterday (2022-04-27):

Summary: There is 3 days delay in implementation of the Developers should have a visualization that can show information from the backend-profiling. (#181930315) task.
It will cause 0 days delay for the delivery of this weekly plan.

Actually 1 day delay + time off.

Delay Cause: Cleaning the hovering text functionality took longer than hoped. (Enso Bot - Apr 28, 2022)

---

**Michael Mauderer** reports a new **STANDUP** for yesterday (2022-04-27):

Progress: Work on fixing hovering labels in a good way for good took a bit longer than expected, but is finished. Note: this is for 2022-04-26 but cannot be submitted for that day anymore. It should be finished by 2022-04-28.

Next Day: Next day I will be working on the #same task. Finish layout and code clean up of the visualisations. Get started on gathering and analysing data for node creation. (Enso Bot - Apr 28, 2022)

---

**Michael Mauderer** reports a new **STANDUP** for yesterday (2022-04-28):

Progress: Finished the draft PR. It should be finished by 2022-04-28.

Next Day: Next day I will be working on the ##181850606 task. Some Performance Team bookeeping: updating designs and creating user stories for the tasks ahead. Also collecting more data for node creation and if time permits posting the insights from that. Note: the next issue will be replaced with a better refined and planned one by the next standup. (Enso Bot - Apr 29, 2022)

---