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

Performance issues #105

Open
bowspider-man opened this issue Oct 31, 2024 · 4 comments
Open

Performance issues #105

bowspider-man opened this issue Oct 31, 2024 · 4 comments

Comments

@bowspider-man
Copy link

I have a dataset of about 1 billion. My machine has a 64-core cpu and 128g memory. I found that with this configuration, I can only deduplicate 30 million data at a time. I would like to ask if there are any parameter settings that can allow me to deduplicate more data at a time while keeping my machine configuration unchanged.

@ChenghaoMou
Copy link
Owner

Which script are you using and how big is your dataset (physically)?

@bowspider-man
Copy link
Author

Which script are you using and how big is your dataset (physically)?

I use this script: python -m text_dedup.minhash, the physical size of my dataset is 4.7T

@ChenghaoMou
Copy link
Owner

I see. Unfortunately, right now, none of the scripts were designed to be used for such a low-memory case directly.

You would need to refactor the script to process the data in partitions and in stages, and it will take longer time to finish. For example, you can read each parquet file iteratively, calculate the hashes, store the results. Then read the hashes to form the graph, maybe even use a database, then find the connected components on top of that.

Copy link

github-actions bot commented Jan 1, 2025

Stale issue message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants