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

[Feature Request] Profiling #1181

Open
bbudescu opened this issue Dec 18, 2024 · 0 comments
Open

[Feature Request] Profiling #1181

bbudescu opened this issue Dec 18, 2024 · 0 comments
Labels

Comments

@bbudescu
Copy link

bbudescu commented Dec 18, 2024

Similarly to the ray dashboard, add capability to generate a flame graph for each task submitted to the dask worker pool, and perhaps, also, some way to view the current stack trace of running processes. I know that ray uses py-spy, but I guess it would be worth taking a look at other profiling tools, too, perhaps like scalene or austin

Motivation: In a concurrent, multiprocessing environment, like, e.g., when using dask clusters to run trials, it's hard to pinpoint exactly where bottlenecks occur, and where workers have to wait on each other or on the main process to release access to shared resources, or to provide some results, like, e.g., suggestions of what configs to try next, which might hang because of high contention either, e.g., on the surrogate model, or on the multi-fidelity intensifier, or something else altogether.

Check out #1169, #1170 and #1178 (comment) for the context in which this feature request has arisen.

LE: Since Python 3.12, the interpreter can generate profiles on linux. Here is a list of some profilers that are currently popular.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

2 participants