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

Change Azure default controller_type and worker_type #539

Merged
merged 1 commit into from
Sep 10, 2019

Conversation

dghubble
Copy link
Member

  • Change default controller_type to Standard_B2s. The B2s is cheaper by $17/month and provides 2 vCPU, 4GB RAM (vs 1 vCPU, 3.5GB RAM)
  • Change default worker_type to Standard_DS1_v2. F1 was the previous generation. The DS1_v2 is newer, similar cost, more memory, and still supports Low Priority mode, if desired

@dghubble
Copy link
Member Author

Over the last week, I've observed this reduces etcd fsync latency on Azure as well, independent of the recent etcd v3.4 update. Azure SSD disk latency is typically worse than what's observed on AWS and Google Cloud (~10ms), but this brings it closer to them (from ~120ms to ~50ms). Its hard to be absolute about this, as Azure's performance isolation is unknown - its possible I've landed on quiet hosts, but I think not, Azure has been in the ~120ms ballpark for months.

* Change default controller_type to Standard_B2s. A B2s is cheaper
by $17/month and provides 2 vCPU, 4GB RAM (vs 1 vCPU, 3.5GB RAM)
* Change default worker_type to Standard_DS1_v2. F1 was the previous
generation. The DS1_v2 is newer, similar cost, more memory, and still
supports Low Priority mode, if desired
@dghubble dghubble force-pushed the change-azure-instance-type-defaults branch from 0acaa3b to 4a7083d Compare September 10, 2019 05:34
@dghubble dghubble merged commit 4a7083d into master Sep 10, 2019
@dghubble dghubble deleted the change-azure-instance-type-defaults branch September 13, 2019 03:21
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.

1 participant