Should I use c: or d: on azure VM? -


I have a blue VM and I can see two drives c: and d: (say temporary storage). Both drives allow me to create project folders and use them from Visual Studio. I would like to know which drive I got, which is a reliable drive I should use - is anyone thinking?

Thanks PL

C: \ drive comes with VM, which That's 127 GB, now nobody else. So this is the root volume and the OS is also installed here, so it is possible that 127GB-40GB can use 70 GB of free space so broadly.

C: \ - Cost: Any additional cost, computation fee comes with

D: \ It is said, it is not stable and when you stop and start the machine, then this volume will be recycled. This drive operates at very high speeds, it is good for temporary file storage etc. You can also use it for logging, if you need to continue those logs, you can run a background job to push it to blue blob or accessories etc. / P>

D: \ - Cost: No additional cost, comes with calculation fee

E: \ F: \ g: \ h : \. .. etc. All can be used for all practical purposes . You will essentially attach a blob

  • One suggestion I can provide is that you can add a blank drive directly to 1TB (for Azure 1023 GB), for the full 1023 GB Will not be billed, but only for the amount of data stored in the drive.
  • This drive is relatively C: \ & amp; D: \, For reasons of latency, it takes longer time to write the wire and then for Blob, directly onto the attached disc itself. But this business is off, which you have to choose for size vs speed.

    E: \ F: \ g: \ h: \ ... - cost: extra cost for storage, transaction / operation < / Blockquote>

Comments

Popular posts from this blog

c - Mpirun hangs when mpi send and recieve is put in a loop -

python - Apply coupon to a customer's subscription based on non-stripe related actions on the site -

java - Unable to get JDBC connection in Spring application to MySQL -