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

find ways to save aws costs #2447

Closed
wrashid opened this issue Mar 24, 2020 · 2 comments
Closed

find ways to save aws costs #2447

wrashid opened this issue Mar 24, 2020 · 2 comments
Assignees

Comments

@wrashid
Copy link
Collaborator

wrashid commented Mar 24, 2020

-> sport instances an option?
-> how to track better, e.g. add tags explicitly to runs?
-> look at current expenses

@wrashid
Copy link
Collaborator Author

wrashid commented Mar 24, 2020

  • add user and project tag. are the searchable in aws cost management?
  • get spot instance running
  • collect data for instance type we use, e.g. how often stopped
  • can we stop on iteration and continue from it?

@zneedell
Copy link
Collaborator

A thought--would it be a big lift to upload and use a default set of mostly relaxed link travel times for SFBay and do a [luke]warm start from those as a default? We waste so many iterations starting from free flow travel times when we have a better prior available of what we expect congestion to look like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants