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

Any suggestions/pipeline process for large text files? #65

Open
CompileZero opened this issue Jul 21, 2021 · 0 comments
Open

Any suggestions/pipeline process for large text files? #65

CompileZero opened this issue Jul 21, 2021 · 0 comments

Comments

@CompileZero
Copy link

I recently provided openSesame a 4MB text file. The predicted_args.conll was about 260MB, and took about 1 complete day (24hours) to annotate entirely.

I now have a 300MB text file which I need to annotate. I am expecting the predicted_args.conll to be about 20GB. The problem here is the processing time. This may process may take-up days/months if run on a single open-sesame instance. Does anybody have any idea as to how we can implement this process as a pipeline?

Maybe run several containers with open-sesame on them, or divide the huge text files into smaller text files, and then annotate each one of them separately? Is there any way in which this task could be achieved in a smaller time duration?

Thanks...

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

1 participant