VM Best Practices: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 25: Line 25:


<!--T:7-->
<!--T:7-->
This has been observed on Arbutus (west.cloud.computecanada.ca) by multiple users, although it may be somewhat dependent on volume size.  In one case, 3 x 100GB volumes attached to a p4-6gb VM caused kernel timeouts whenever disk operations of any magnitude were attempted.  It was very difficult to copy more than 500MB of data between two filesystems, for example.
This has been observed on Arbutus (arbutus.cloud.computecanada.ca) by multiple users, although it may be somewhat dependent on volume size.  In one case, 3 x 100GB volumes attached to a p4-6gb VM caused kernel timeouts whenever disk operations of any magnitude were attempted.  It was very difficult to copy more than 500MB of data between two filesystems, for example.


<!--T:8-->
<!--T:8-->
Test of a similar situation was performed on East Cloud and with 4 x 100GB data volumes (along with the root volume), the same OS and a similar VM flavour, the issue did not occur.  This VM had more memory (15 GB instead of 6 GB) but high memory usage was not observed in the Arbutus case and this isn't believed to be a factor.
Test of a similar situation was performed on East cloud and with 4 x 100GB data volumes (along with the root volume), the same OS and a similar VM flavour, the issue did not occur.  This VM had more memory (15 GB instead of 6 GB) but high memory usage was not observed in the Arbutus case and this isn't believed to be a factor.
</translate>
</translate>
[[Category:CC-Cloud]]
[[Category:CC-Cloud]]
rsnt_translations
56,430

edits

Navigation menu