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

Add cpu utilization as a parameter with which desires can be obtained #74

Merged
merged 2 commits into from
Oct 26, 2023

Conversation

ramsrivatsa
Copy link
Contributor

@ramsrivatsa ramsrivatsa commented Oct 13, 2023

Use CPU utilization directly within extra model arguments. If we have utilization numbers, we can directly leverage them to obtain desired instance types. If we don't, then use the default reads and writes to compute CPU util which in turn can be used to obtain desired instance types.

Also added pytest in the setup so that it can integrate seamlessly with pycharm.

@ramsrivatsa ramsrivatsa force-pushed the ramsrivatsak/cpu-utilization-cass branch from 2c09f54 to 352a776 Compare October 13, 2023 16:50
@ramsrivatsa ramsrivatsa changed the title Add cpu utilization as a parameter in extra model arguments; If you h… Add cpu utilization as a parameter with which desires can be obtained Oct 13, 2023
@abersnaze
Copy link
Contributor

i noticed a lot of whitespace change. @jolynch what is there a formatter that you used?

@abersnaze
Copy link
Contributor

I don't think the model should be aware what the current instance is.

I would like to see the current instance to be used as signal to the planner that one of the least_regret plans must be of that instance. that way we could:

  • compare what the planner thinks should deploy vs what is.
  • compare replans vs alternatives.

this also introduces more challenges to compositions of models since a kv cluster would likely have a different current instance than the composed cassandra. I'm thinking we should depreciate composition and have the client invoke the planner for each model separately.

service_capacity_modeling/interface.py Outdated Show resolved Hide resolved
service_capacity_modeling/interface.py Outdated Show resolved Hide resolved
setup.py Outdated Show resolved Hide resolved
@ramsrivatsa ramsrivatsa force-pushed the ramsrivatsak/cpu-utilization-cass branch 4 times, most recently from 4cbb8a5 to ffb2e55 Compare October 24, 2023 22:29
@abersnaze abersnaze force-pushed the ramsrivatsak/cpu-utilization-cass branch from ffb2e55 to a76552e Compare October 24, 2023 22:43
@ramsrivatsa ramsrivatsa force-pushed the ramsrivatsak/cpu-utilization-cass branch from a76552e to 67413e8 Compare October 24, 2023 22:56
…pes (+5 squashed commits)

Squashed commits:
[aa15bd9] joey changes on new types
[592def6] consolidate current instance type (str), count (interval), cpu% (interval) into a new model object
[82dd4c5] required cluster type parameter is now per zone
[0ce2064] Moved instance type definition inside interface (joey comments addressed)
[352a776] Add cpu utilization as a parameter in extra model arguments; If you have cpu usage already use it directly
@ramsrivatsa ramsrivatsa force-pushed the ramsrivatsak/cpu-utilization-cass branch 2 times, most recently from d953a3b to fac3418 Compare October 26, 2023 00:00
@ramsrivatsa ramsrivatsa force-pushed the ramsrivatsak/cpu-utilization-cass branch from fac3418 to de475e0 Compare October 26, 2023 02:12
@ramsrivatsa ramsrivatsa merged commit f819b9d into main Oct 26, 2023
6 checks passed
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 this pull request may close these issues.

None yet

3 participants