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

Horizontal scaling #156

Closed
inz opened this issue Oct 1, 2016 · 5 comments · Fixed by #159
Closed

Horizontal scaling #156

inz opened this issue Oct 1, 2016 · 5 comments · Fixed by #159
Assignees

Comments

@inz
Copy link
Collaborator

inz commented Oct 1, 2016

Create a MiniZinc model for horizontal scaling and an according recommendation job.

(UI will need slight adjustment as well)

@inz inz self-assigned this Oct 1, 2016
@inz
Copy link
Collaborator Author

inz commented Oct 7, 2016

Do we want to generate both, vertical and horizontal scaling recommendations?

@gmazlami
Copy link
Contributor

gmazlami commented Oct 7, 2016

I think we should make it optional, i.e. the user can choose whether to use horizontal or vertical scaling.

@inz
Copy link
Collaborator Author

inz commented Oct 7, 2016

Right. The only "problem" I have with the current vertical scaling recommendations is that we essentially recommend deployment topologies that consist entirely of SPOFs 😉

We could also let users limit the number of recommended instances per ingredient (as a constraint specified with the workload model. or based on the ingredient type, i.e., RDBMS <5 instances, etc.).

@inz
Copy link
Collaborator Author

inz commented Oct 7, 2016

Also, with horizontal scaling, the graph got a bit more "boring" 😉

screen shot 2016-10-07 at 5 21 26 pm

@gmazlami gmazlami closed this as completed Oct 7, 2016
@inz inz reopened this Oct 7, 2016
@inz
Copy link
Collaborator Author

inz commented Oct 7, 2016

I'd like to discuss this further and leave the issue open at least until I open the pull request

@inz inz mentioned this issue Oct 10, 2016
@inz inz added this to the Sensitivity Analysis v1.0 milestone Oct 13, 2016
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

Successfully merging a pull request may close this issue.

2 participants