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

Update Standard.json for OsDisk #24

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

jasbryan
Copy link

Modified OS disk to SSD drive.

Modified OS disk to SSD drive.
@jasbryan jasbryan mentioned this pull request Jan 24, 2019
@jasbryan
Copy link
Author

It is working now. Please give it a try and let me know what you think.

@ecalder6
Copy link
Owner

ecalder6 commented Feb 1, 2019

Gave it a shot. I'm not sure if the VM is using an SSD based on the benchmark below. What do you think?

benchmark

@jasbryan
Copy link
Author

jasbryan commented Feb 1, 2019

Looks pretty badass to me. I have been running it with the SSD for a few weeks. Runs great. You really need it for big games. I play Star Citizen and it is going to the drive all the time. I wish I could force more into RAM since these VMs have so much.
There are even faster SSD options available but I have not compared them.

@jasbryan jasbryan closed this Feb 1, 2019
@jasbryan
Copy link
Author

jasbryan commented Feb 1, 2019

Meant to request merge not to close it.. I am new to GitHub..

@ecalder6
Copy link
Owner

ecalder6 commented Feb 1, 2019

No worries. I'll test a bit more and merge it.

@ecalder6 ecalder6 reopened this Feb 1, 2019
@ecalder6
Copy link
Owner

ecalder6 commented Feb 8, 2019

Here's the speed I got with the current code:
image

I don't think changing the storage account type to StandardSSD_LRS changes the disk to SSD. I'm pretty sure you'll have to deploy NVv2 VMs for SSD: https://azure.microsoft.com/en-us/updates/public-preview-new-gpu-enabled-nvv2-azure-vms-for-graphics-intensive-applications/

@ecalder6 ecalder6 self-requested a review February 8, 2019 18:24
Copy link
Owner

@ecalder6 ecalder6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SSD is not deployed.

@jasbryan
Copy link
Author

jasbryan commented Feb 8, 2019

When I am running with this configuration my Disk shows standard SSD. IT is not the new, faster advanced SSDs but the standard ones.

@ecalder6
Copy link
Owner

ecalder6 commented Feb 8, 2019

My tests show that there isn't a difference in speed to justify the change. Feel free to do some speed comparisons yourself to show the performance gain.

@jasbryan
Copy link
Author

I ran comparison tests with an HDD and an SSD mounted and there were noticeable speed increases.
Here is the comparisons.

MultipleDiskReport.zip

@ecalder6
Copy link
Owner

Thanks for the comparison! How did you setup your test environment? Are both C and E drive managed disks?

@jasbryan
Copy link
Author

I beleive they are both managed disks. I just added the HDD drive and then ran the test on both. So the C drive was still running the OS during the test and was still much faster.

image

@ecalder6
Copy link
Owner

Nice. So just to confirm, C drive is the Standard SSD that's deployed using your change, and E drive is the Standard HDD that you've added through the portal/powershell?

If so, my test methodology is a bit different. I've deployed a VM using your changes and a VM using the current code and compared the speed of the two C drives using CrystalDiskMark. Could you try testing it this way (don't really care about the software used) to make sure the drive deployed with your change performs better than the drive deployed currently? I could also test again as well when I get a chance.

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.

2 participants