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.

Sign up for GitHub

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

Jump to bottom

classification with gridType="linear" causes slowdown for parallel execution #190

Open
ghost opened this issue Nov 28, 2019 · 0 comments
Open

classification with gridType="linear" causes slowdown for parallel execution #190

ghost opened this issue Nov 28, 2019 · 0 comments
Labels
bug Crashes, freezes, compilation/run-time errors, undesirable behavior, wrong info in help/docs needs confirmation Issues that should be reproduced by another user (not the submitter), default for new issues

Comments

@ghost
Copy link

ghost commented Nov 28, 2019

Issue

"gridType"="linear" significantly slows down parallel execution of classification

Reproducing

e.g. from /datadriven/examplesPipeline/ execute

mpirun -n 4 ./ParallelMiner config_parallelClassification.json

while setting "fitter" : "gridConfig" : "gridType"="linear" in the config.

Remarks

Other parameters than gridType seem not to influence the issue. Setting "gridType"="modlinear" causes no issue.

It seems to be caused by DBMatOnlineDE::computeDensityFunctionParallel in the lines 289 - 298, as replacing them with the non parallel version solves the issue.
@valentjn valentjn added bug Crashes, freezes, compilation/run-time errors, undesirable behavior, wrong info in help/docs needs confirmation Issues that should be reproduced by another user (not the submitter), default for new issues labels Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Crashes, freezes, compilation/run-time errors, undesirable behavior, wrong info in help/docs needs confirmation Issues that should be reproduced by another user (not the submitter), default for new issues
Milestone
No milestone
Development

No branches or pull requests
1 participant
@valentjn