Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the information available to debug performance issues #4338

Open
sbegaudeau opened this issue Dec 20, 2024 · 1 comment · May be fixed by #4342
Open

Improve the information available to debug performance issues #4338

sbegaudeau opened this issue Dec 20, 2024 · 1 comment · May be fixed by #4342

Comments

@sbegaudeau
Copy link
Member

We are missing key data in order to identify performance issues, the following pieces of information should be added and/or documented:

Frontend

  • log the time taken by the layout
  • Log the time taken by some core components of our representations (tree, form, diagram, table) using the React profiler

Backend

  • log time of each event handler
  • log time of the IEditingContext{Persistence|Search}Service
  • log time of each IRepresentationEventProcessor#refresh
  • log time (with a threshold) of the evaluation of AQL expressions (log all expressions taking more than 50ms for example)
  • log the time taken by each datafetcher using GraphQL Java instrumentation support

All this should be done with some easy to use configuration properties on the backend (to start debugging everything easily)

@sbegaudeau
Copy link
Member Author

As a result of this issue, some documentation should be available along with some default settings in Sirius Web to run an instance of Sirius Web with all performance log activated.

sbegaudeau added a commit that referenced this issue Dec 21, 2024
sbegaudeau added a commit that referenced this issue Dec 22, 2024
sbegaudeau added a commit that referenced this issue Jan 2, 2025
sbegaudeau added a commit that referenced this issue Jan 2, 2025
sbegaudeau added a commit that referenced this issue Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant