vFoglight Sizing & Scalability - Part 2

Author: Thomas Bryant III, Vizioncore Senior Product Architect

Continuing from the last post, we are now going to explore installing vFoglight 5.2.6 into a VM and start pointing vCenters at it.


For the purpose of the test I'm using the following configurations to start and we will grow it as we add more vCenters and thus more VMs or as performance dictates.

vFoglight VM
OS - Windows 2003 R2 x86_64
vCPUs - 2
Memory - 2G
Hard Drives - 3 VMDKs on Raid Group 2 (only VMDKs on the Datastore)
10G C:\ (OS Partition - 64k aligned)
5G D:\ (Swap Partition 4G Fixed size - 64k aligned)
30G F:\ (Application Partition - 64k aligned)
vFoglight 5.2.6 x86_64

Physical Hardware
Dell T610
OS - vSphere 4.0
CPUs
- 2x Intel Nehalem L5520 @ 2.27Ghz (8 Cores + 8 HT = 16 Logical CPUs)
Memory - 32G
Disks - 3 RAID1 Groups
Group1 = 2x 146G 15K RPM SAS
Group1 = 2x 146G 15K RPM SAS
Group3 = 2x 1.5TB 5400 RPM SATA

A little house keeping before we get into some data. I've chosen to go with the x86_64 version of vFoglight, and intentionally I've undersized the requirements to allow us to show a single host and how it can scale to large environments. As with many 64-bit applications, the memory requirements essentially double vs. 32-bit applications as they require a larger foot print right away to handle more memory pages. The default behavior of a JVM is to allow for utilization of 75% of total system memory. For example, below you will see figures around the JVM with top at 1.5G for possible use in the JVM when the total system memory is 2G.

After downloading vFoglight 5.2.6, I simply followed the installation process doing a custom install and changing the paths to F: instead of C: as that is where I want to place the vFoglight application. This is good for many reasons, but one of the main reasons is it allows me to easily see the Disk IO for the entire application.

FIrst up, a single vCenter with 1 ESX host and 30 Virtual Machines. After configuring the collector to talk to this vCenter, it does the heavy lifting of getting the data over to the vFoglight Management Server. Below in Figure 1 & Figure 2 you will see the memory required to run the Management Server, collect the metrics and then the load of the FMS as we see from within the application.


As you can see, the system is easily handling this small load effectively. This screen is viewable, as well as lots of other important statistics on your vFoglight server under Dashboards - Foglight - Diagnostic -Performance - Overview. Next up, I'll be adding another 70 so VMs, to take us up to around 100 VMs and then how many more VM's can we add before adding more memory on our way to 1000 VMs and beyond.


To be continued...


Thomas Bryant III
Vizioncore Senior Product Architect

Anonymous