add NoDB for non-recording Hub #1267
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When used, this disables database-based actions in the Hub. Useful for minimizing Hub memory consumption.
|
I read through the diffs and this looks great. The code is simple and the documentation is very complete. I think this is a very nice performance optimization. I would go ahead and merge whenever you want. |
minrk
added a commit
that referenced
this pull request
Jan 16, 2012
add `--nodb` option for non-recording Hub This allows simple use cases to avoid needing to call `purge_results` to prevent memory growth of the Hub.
minrk
added a commit
that referenced
this pull request
Jan 18, 2012
add `--nodb` option for non-recording Hub This allows simple use cases to avoid needing to call `purge_results` to prevent memory growth of the Hub.
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this pull request
Nov 3, 2014
add `--nodb` option for non-recording Hub This allows simple use cases to avoid needing to call `purge_results` to prevent memory growth of the Hub.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When used, this turns database-writes into no-ops, and raises KeyErrors on accesses.
Useful for minimizing Hub memory consumption under high load.
Any request for db-stored information will fail:
rc.hub_history()rc.resubmit()rc.db_query()rc.get_result()for tasks submitted by other Clients.The real database backends have good memory behavior for long-running clusters, but are poor when lots of data is flowing through the schedulers, because they are too slow to push data to the database.