WIP - MTV-1352: Documentation of MTV performance 2.6

[anarnold97]

JIRA

• MTV-1352

PREVIEW

• MTV performance recommendations
• MTV performance addendum

[mordechai]

Following comments for: https://anarnold97.github.io/MTA-Preview/MTV/mtv-performance.html#mtv-performance-recommendation_mtv

Suggestion 1)
Line currently reads 'When more ESXi servers are used, high datastore read rates are possible.'
I think could be reworded to 'When multiple ESXi servers are used, higher datastore read rates are possible.

Suggestion 2)
Line currently reads " Testing showed that when transferring more than 10 VMs with both BIOS and host power management set accordingly, dataset read rates between tested VMs increased by 15 MiB."
I think could be reworded to " Testing showed that when transferring more than 10 VMs with both BIOS and host power management set accordingly, migrations had an increase of 15 MiB in the average datastore read rate."

Suggestion 3)
Line current reads " Maximum migration transfer rate of a single disk: 162 MiB/second (1.5 Tb case / time using utilized data) "
I think could be reworded to: "Maximum migration transfer rate of a single disk: 162 MiB/second (rate observed when transferring 1.5T of non-zero data) "

Suggestion 4)
Line reads: " In MTV 2.6, MAX_VM_INFLIGHT reserves one transfer slot per VM, regardless of current migration activity for a specific snapshot. The total set by MAX_VM_INFLIGHT is used to utilize one slot.

Example

MAX_VM_INFLIGHT = 20 and 2 ESXi hosts defined in the provider mean each host can transfer 20 VMs. "

I think could be reworded to: " In MTV 2.6, MAX_VM_INFLIGHT reserves one transfer slot per VM, regardless of current migration activity for a specific snapshot or the number of disks that belong to a single vm. The total set by MAX_VM_INFLIGHT is used to indicate how many concurrent VM tranfers per ESXi host is allowed.

Example

MAX_VM_INFLIGHT = 20 used with 2 ESXi hosts defined in the provider implies that each host can transfer 20 VMs. "

Suggestion 5)
In section 3.4.5
Line reads: "The migration of the differences between snapshots happens over specific intervals before a final cut-over of the running VM to openshift occurs."
I think the o should be capitalized for Openshift "The migration of the differences between snapshots happens over specific intervals before a final cut-over of the running VM to _O_penshift occurs."

In https://anarnold97.github.io/MTA-Preview/MTV/mtv-performance.html#mtv-performance-addendum_mtv

Suggestion 6)

There are various references to the private network such as:
172.x Network or 172.16.x.x Network I think these references should just be replaced with Private Network
with a foot note that explains Private Network is a non -Management network .

[fabiand]

Can we move this into it's dedicated section, aka level it up?

Mostly to avoid deep nesting.

To me it could be a sectoin just before Troubleshooting