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

Do not create a new Thread in a new ThreadGroup when performing an execution. #84

Closed
XerTheSquirrel opened this issue May 30, 2018 · 0 comments
Assignees
Labels
refactor Refactoring! review In review or needs reviewing
Milestone

Comments

@XerTheSquirrel
Copy link
Contributor

To handle the profiler profiling only a given execution I had to create a new ThreadGroup and spawn a new thread for every invocation that occurs. This creates some overhead so I am very much in the idea that this should be reversed and instead having a thread monitor of sorts or attachment. This should decrease latency and allow executions to perform faster. As a result the profiler will not have a good idea of which threads belong to a given execution if they are unflagged, but this might not be too much of an issue since the information might be wanted anyway.

This is related to #77.

@XerTheSquirrel XerTheSquirrel added the refactor Refactoring! label May 30, 2018
@XerTheSquirrel XerTheSquirrel self-assigned this Jul 31, 2018
@XerTheSquirrel XerTheSquirrel added in progress Development is currently in progress! review In review or needs reviewing and removed in progress Development is currently in progress! labels Jul 31, 2018
Java Refactoring and Optimization automation moved this from To Do to Done Aug 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor Refactoring! review In review or needs reviewing
Projects
No open projects
Development

No branches or pull requests

1 participant