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.

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

spin down inactive Engines #13

Closed
gburgett opened this issue Dec 28, 2012 · 0 comments
Closed

spin down inactive Engines #13

gburgett opened this issue Dec 28, 2012 · 0 comments
Milestone
version 1

Comments

@gburgett
Copy link
Owner

Right now, once an engine spins up it is up until the database shuts down. We should be able to spin down engines that haven't been used in a while, by the last activity date.

This may require a change in the way Tables get their Engines, since right now it's injected but I suspect Tables will be dependency-injected themselves so we can't rely on them being temporary.

This could tie in as a precursor to #11, but I'd like to have this done for version 1.
gburgett added a commit that referenced this issue Jan 8, 2013
@gburgett
close to fixing #13
4d50003 
I want to do a couple unit tests, which means I need to abstract out the engine creation in the database.  I was planning to do this anyways.

Signed-off-by: gburgett <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
version 1
Development

No branches or pull requests
1 participant
@gburgett