Skip to content

Too big of runtime #105

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.

Sign up for GitHub

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

Jump to bottom
Closed
ericmjonas opened this issue Mar 26, 2017 · 3 comments
Closed

Too big of runtime #105

ericmjonas opened this issue Mar 26, 2017 · 3 comments
Assignees
@ericmjonas
Labels
runtime
Milestone
v0.3

Comments

@ericmjonas
Copy link
Collaborator

If a user creates a runtime that unpacks to be too large, make sure we deliver sane errors to the user.
@ericmjonas
Copy link
Collaborator Author

In particular the wrenhandler tries to download the pickled objects like data and the function before it deals with the handler. So this is a problem for multiple reasons

  • If func or data is too large, we will error
  • if there is left-over crap from a previous run, we will error

@ericmjonas
Copy link
Collaborator Author

A reasonable workaround if the runtime ate up too much space on the last invocation can be to call map with use_cached_runtime=False

@shivaram shivaram added this to the v0.3 milestone Mar 29, 2017
@ericmjonas ericmjonas mentioned this issue Aug 25, 2017
Merged
@ericmjonas
Copy link
Collaborator Author

Closed by PR #172

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ericmjonas ericmjonas

Labels
runtime
Projects
None yet
Milestone
v0.3
Development

No branches or pull requests
2 participants
@ericmjonas @shivaram