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

parallelize upload #4

Open
nherment opened this issue May 12, 2014 · 2 comments
Open

parallelize upload #4

nherment opened this issue May 12, 2014 · 2 comments

Comments

@nherment
Copy link
Contributor

can we have a --parallel <integer> option to run the import in parallel (children processes) ?

Trello Card

@mcollina
Copy link
Contributor

Is the import CPU-bound at them moment, or is it I/O-bound? Is the CPU running at 100% when importing?
In that case, we do not need children processes, we just need to do more than one seneca call at the same time, as it should be I/O-bound at the moment.

The best way to handle it is to have multiple insert running in parallel, i.e. we forward up to N calls to seneca at the same time. I think it's feasible.

Do you have an ETA for this? This week is incredibly tough for me.

@nherment
Copy link
Contributor Author

The import is IO bound and I suspect it is IO protocol bound :) --> I suspect the latency to be killing us, hence the child processes 'workaround'.
We probably make too many requests but we can't really batch either, yet. At some point I think the seneca DB layers should provide batching.

no rush for this.

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