VMware CLOUD DIRECTOR 1.0 Manuel d'utilisateur télécharger pdf (Page 19)

PERFORMANCE STUDY /19

VMware vCloud Director 1.0 Performance and Best Practices

Results

Copying OVF packages directly between two datastores or within the same datastore is much faster than the

approach of uploading OVF packages. Figure 15 shows the latency trends for the three configurations.

The last bar is for Figure 12, where the destination organization vDC does not have access to the source datastore

on which the source vApp template resides. At almost eight minutes (488 seconds), this setup has the highest

latency. In contrast, the first and second bars (for the configurations shown in figures 13 and 14) show a large

improvement at close to 1 minute.

VM clones can be completed eight times faster when the datastore setup is correctly designed.

Figure 15. VM Clone Latency for Different Datastore Setups

For the first two bars in Figure 15, the latency numbers are almost the same as the ones achieved directly through

vSphere. This shows that the additional time required by vCloud Director is negligible for VM clone operations

when compared with the time taken to clone VMs in vSphere.

Performance Tuning Tips

To achieve better performance for VM clones in vCloud Director 1.0, we recommend having a central datastore to

hold the most popular vApp templates and media files and have this datastore mounted to at least one ESX host

per cluster. This way, the destination organization vDC has access to both the source and destination datastores.

This removes the need to copy the OVF package files twice as discussed in “OVF File Upload” on page 10.

100

200

300

400

500

600

same datastore shared

between org vDC

source datastore shared

but destination data store

is different

destination org vDC has no

access to source data

store

Latency in Seconds

1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 31 32

Pas de commentaire

VMware CLOUD DIRECTOR 1.0 Manuel d'utilisateur Page 19