Versions Compared

Old Version 2

changes.mady.by.user Sowmya Krishnan

Saved on

compared with

New Version 3

changes.mady.by.user Sowmya Krishnan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Following are some of the Baseline Performance Run Results of runs done pre-4.x. 

CONFIGURATIONS

...

This shows the time taken for the job id to return in response to the Deploy VM async job. The average time taken across Deploy VM API calls is 0.7 sec and the Median value is 0.418. This means, most API calls took < 0.418 sec to return the job id 

 
Graphs for Deploy VM:

Image Added Image Added

Use case 2: Steady State Measures

...

The highlighted area shows the readings taken during Deploy VM. The graphs cover a total time of around 9 hours (including deploy VM which took ~ 3 hours)  Image Added

MS RESTARTS

 

direct.agent.load.size

Time for all hosts to connect to MS2
after stopping MS1

Time for all hosts to get disconnected
after stopping MS2

Time for all hosts to connect to
MS1 after it is started

Time for rebalancing the hosts between
the two MSs

500

460 s

135 s

120 s

265 s

1000

140 s

50 s

100 s

202 s

...

  1. Hourly snapshots for 1000 Volumes## Snapshots were triggered for all 1000 VMs and the job ids were all generated within the 300 sec interval before the next poll begun.
  2. Hourly Snapshots for 10000 Volumes## Snapshots were triggered for all 10000 Volumes. But the time taken was beyond 300 sec. So the polling continued only after all snapshots were triggered. 

 

Following graph shows the CPU Utilization during snapshots being triggered (for 10000 volume case)

Image Added