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

lot of memory allocations becomes bottleneck #120

Open
jkr0103 opened this issue Nov 9, 2022 · 4 comments · May be fixed by #133
Open

lot of memory allocations becomes bottleneck #120

jkr0103 opened this issue Nov 9, 2022 · 4 comments · May be fixed by #133
Labels
enhancement New feature or request

Comments

@jkr0103
Copy link

jkr0103 commented Nov 9, 2022

I captured perf data for most of the algorithms and see there are lot many memory allocations happens during the run which become bottleneck. Please refer attached screenshot.

Is there a way to fine tune the memory allocations? like any env variable or cmmandline arguments?

perf data for nusvc

@Alexsandruss
Copy link
Contributor

Memory allocations are expected especially during generation of synthetic datasets.
I can't add anything else without knowledge of what are you exactly running on this screenshot.
There is no variable or argument to control it.

@jkr0103
Copy link
Author

jkr0103 commented Nov 11, 2022

Is it possible to split the "generation of synthetic datasets" and "actual benchmark execution" between two processes. My case is I am trying to run these benchmarking algorithms in SGX using gramine where we have memory constraints. Hence would like to know if synthetic datasets can be generated separately so that we do only benchmarks execution inside SGX.

@jkr0103 jkr0103 closed this as completed Nov 11, 2022
@jkr0103 jkr0103 reopened this Nov 11, 2022
@jkr0103
Copy link
Author

jkr0103 commented Nov 11, 2022

sorry closed it by mistake

@napetrov napetrov added the enhancement New feature or request label May 16, 2023
@napetrov
Copy link
Contributor

Would be addressed with pre-fetch capability in this PR -#133

@Alexsandruss Alexsandruss linked a pull request May 17, 2023 that will close this issue
@Alexsandruss Alexsandruss linked a pull request May 17, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants