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

Profile and optimize implementation of GEKPLS #362

Open
vikram-s-narayan opened this issue Jun 26, 2022 · 3 comments
Open

Profile and optimize implementation of GEKPLS #362

vikram-s-narayan opened this issue Jun 26, 2022 · 3 comments

Comments

@vikram-s-narayan
Copy link
Contributor

Profile implementation of GEKPLS and analyze and fix bottlenecks.

@Spinachboul
Copy link
Contributor

Tasks done

I profiled the function GEKPLS and identified the potential bottlenecks, which might be causing heavy memory usage:

  • abstractinterpretation.jl
  • typeinfer.jl
  • boot.jl

And upon individual inspection, I discovered that the function _ge_compute_pls might be the most heavily resourceful function for which I will provide the profiling information soon.

@ChrisRackauckas & @vikram-s-narayan
Please look into the flame graph and suggest any possible changes!!

Here is the link to the notebook:
https://julianotebook.w3spaces-preview.com/index.html

flame_graph

@ChrisRackauckas
Copy link
Member

It looks like you included compilation in the profiling.

@Spinachboul
Copy link
Contributor

Yeah! I just tried to profile the whole function to get a high-level view of memory storage and time consumption.
I am working on gekpls.jl where I would suggest a suitable sampling technique for based on rmse scores for different sampling methods.

It looks like you included compilation in the profiling.

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