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

Avoid using the task queue for immediate values. #4

Open
tkaitchuck opened this issue Oct 17, 2014 · 0 comments
Open

Avoid using the task queue for immediate values. #4

tkaitchuck opened this issue Oct 17, 2014 · 0 comments

Comments

@tkaitchuck
Copy link
Contributor

Currently pipeline triggers a taskqueue request many more times than it really needs.
E.g. creating a child job with N immediate values and 1 future value will trigger N taskqueue "VALUE FILLED" requests where actually none is really needed in this case.

We optimize, this by simply detecting they are immediate results and inlining the call.

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

1 participant