Which task will improve the network performance of this virtual machine?

Refer to the exhibit.

An administrator has received reports of poor network performance with a virtual machine.
Which task will improve the network performance of this virtual machine?

Adjust shares for the virtual NIC on the virtual machine

Traffic-shape this virtual machine

Increase memory to the virtual machine

Add an uplink to the virtual switch that this virtual machine is attached to

11 Comments on “Which task will improve the network performance of this virtual machine?

  1. sajid shaikh says:

    Hi Admin,

    I think option B (Traffic-shape this virtual machine) should be correct answer as exhibit shows high newtork traffic transmitted.

    We can use traffic shaping policy to to reduce the contention.

    Please Reply and Explain.

  2. Alex says:

    improve the network performance of this virtual machine

    I think traffic sharp is limit network performance and free up resource for other vm.

  3. Dave says:

    Wouldn’t traffic shaping on that specific VM continue to affect more poor network performance? The question appears to be specific to the VM which could be sharing vmnic uplink with other VM’s affecting throughput. Additional uplink would add more capability to the vswitch providing more better network performance. If it mentioned poor performance on the vswitch I would recommend the traffic shaping then, correct?

  4. Francesco says:

    I think that the correct answer is D because traffic shaping limit only outbound traffic an not incoming(in this case peak is on Received traffic)

    ESXi allows you to shape outbound traffic on standard switches. The traffic shaper restricts the network bandwidth available to any port, but may also be configured to temporarily allow “bursts” of traffic to flow through a port at higher speeds.


  5. Emiliano says:

    I think is not possible traffic-shape a virtual machine. You can just traffic-shape a vswitch or a port-group, so the correct should be D

  6. gomgom says:

    if you add more uplinks, there’s no guarantee performance will be enhanced. According to the teaming policy, if using the default Route based on virual port ID, this VM will always use a single uplink even if the vSwitch has many active uplinks.
    Traffic shaping is applied to egress traffic, which is in this case, traffic from the vSwitch to the VM. From the VM’s point of view, that’s received packets. so this may help.

  7. Rafael says:

    A – not possible to set/adjust shares on vNIC

    B – Traffic shape VM’s traffic; though on standard switch, this can only be done outbound, on a port-group – so yes this means from the vSwitch towards the VMs. In real world, just adding traffic shaping would solve the problem temporarily – this is because of how customer contracts role sometimes; setting traffic shaping may not be an option in the real-world. I guess vmware is looking here for a more practical/generic answer

    C – Increase memory to the VM – I dont see how would this help at all

    D – Add an uplink to the virtual switch that this virtual machine is attached to – again, not sure how practical this is! adding an uplink, means another physical port which may not be available.

    In another version of the question, there is another answer which is to add the VM to another vSwitch – this is not clear either; it depends really – would the new switch have more uplinks?? This would also depend on the IT Policy in place … and I could think of few more issues … in a nutshell, not easily doable.

    Out of all the options listed, “Traffic Shaping” is the most doable, even though it would give a temporary fix.

  8. jackal99a says:

    QUESTION CLEARLY STATE Improve (INCREASE – Make Better) performance ON the VM – Not the network…. So adding a NIC would be the only way to do that… PLUS we are hearing Network Performance issues…has to assume that we have saturation.

    But FUCK you vmware… Who make desicion based on 1 metric..

Leave a Reply

Your email address will not be published. Required fields are marked *