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

Define additional data capture to profile and understand Studio slowdown #3093

Open
rtibbles opened this issue Apr 12, 2021 · 3 comments
Open

Comments

@rtibbles
Copy link
Member

No description provided.

@rtibbles
Copy link
Member Author

Ideas so far:

Manual data capture:

  • Exporting HAR files from the network tab to understand network traffic when this happens.
  • Doing a memory profile to see what is going on memory wise.
  • Doing debug logging from indexedDB to add timing information for queries, and then asking them to look at the console with debug log filtering.
  • Chrome Task Manager memory usage

Automatic data capture:

@pratykshg9999
Copy link

i want to work on this issue @rtibbles

@marcellamaki
Copy link
Member

Hi @pratykshg9999 - thank you for your interest in contributing! As you can see from the empty issue description, this issue is not yet ready for someone to take it up because there are some notes in the thread but no details yet in the actually issue body.

I know that most of our "help wanted" issues are currently assigned to other community contributors, which may be frustrating, but please use that as a reference when looking for issues that are suitable for the open source community. We will continue to open and tag issues for community contribution now that we have returned from our 2 week end of year office closure, and there will be more opportunities for your contributions in the coming weeks. Happy new year!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants