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

huge memory being used #63

Open
deter3 opened this issue Aug 5, 2016 · 2 comments
Open

huge memory being used #63

deter3 opened this issue Aug 5, 2016 · 2 comments

Comments

@deter3
Copy link

deter3 commented Aug 5, 2016

I did testing for 389 images with 400k 128 dimensions sift key points features .

It took over 10gb ram and used 15gb swap memory , eventually my ssd was out of storage and process went dead without error information .

I reduced to half of images with 200k 128 dimensions sift key points features . Same thing happened .
is there any solution I can fix it ?

@bpkent
Copy link
Collaborator

bpkent commented Aug 5, 2016

The current implementation is geared toward ease-of-use much more than scalability, so I'm afraid there isn't currently a great workaround. At the moment, the best way is to cluster your dataset from the top down and run DeBaCl on each cell of the partition.

@deter3
Copy link
Author

deter3 commented Aug 8, 2016

Thanks for the reply . I figured DeBaCI clustering quality is better than HDBSCAN , and easier to manage , but just memory and time to process are the bottleneck .

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

2 participants