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

Add support for profiles w/ multiples processes & threads #130

Merged
merged 19 commits into from
Aug 12, 2018

Conversation

jlfwong
Copy link
Owner

@jlfwong jlfwong commented Aug 12, 2018

More broadly, this just supports multiple profiles loaded into the editor in the same time, which supports import from profiles which are multithreaded by importing each thread as a different profile.

For now, the only two file formats that support multiprocess import are Instruments .trace files and speedscope's own file format

In the process of doing this, I refactored the container code considerably and extracted all the dispatch calls into containers rather than them being part of the non-container view code. This is nice because it means that views don't have to be aware of which Flamechart they are or which profile index is being operated upon.

Fixes #66
Fixes #82
Fixes #91

@coveralls
Copy link

coveralls commented Aug 12, 2018

Coverage Status

Coverage decreased (-0.4%) to 38.711% when pulling cdee9b3 on jlfwong/multiprocess into 7368e15 on master.

@jlfwong jlfwong merged commit 0e2041c into master Aug 12, 2018
@jlfwong jlfwong deleted the jlfwong/multiprocess branch August 12, 2018 05:01
jlfwong added a commit that referenced this pull request Aug 12, 2018
More broadly, this just supports multiple profiles loaded into the editor in the same time, which supports import from profiles which are multithreaded by importing each thread as a different profile.

For now, the only two file formats that support multiprocess import are Instruments .trace files and speedscope's own file format

In the process of doing this, I refactored the container code considerably and extracted all the dispatch calls into containers rather than them being part of the non-container view code. This is nice because it means that views don't have to be aware of which Flamechart they are or which profile index is being operated upon.

Fixes #66
Fixes #82
Fixes #91
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

Successfully merging this pull request may close these issues.

2 participants