Skip to Content

Scalability for Windows Azure

BMC PATROL for Windows Azure has been tested to scale using 5 accounts, each having 4 hosted services. Each hosted service can contain 5 role instances, with

  • Approximately 1650 parameters per account
  • 82 parameters per role instance
  • Approximately 8250 parameters in total
  • Collection interval for inventory data set to 1 minute
  • Collection interval for role instance AZURE_ASP_NET and AZURE_ASP_NET_APP application classes performance data set to 5 minutes
  • Collection interval for role instance AZURE_SYSTEM, AZURE_GLOBAL_IIS, and AZURE_ASP_NET_STATE_SERVICE application classes performance data set to 3 minutes

  • Collection interval for role instance AZURE_LOGICAL_DISK, AZURE_MEMORY, and AZURE_PROCESSOR application classes performance data set to 2 minutes 

    Warning

    Note

    BMC recommends that you set the Java Heap settings as follows:

    • Initial heap size for the Java collector process = 256 Megabytes
    • Max heap size for the Java collector process = 300 Megabytes

    Scalability is directly proportional to the number of role instances, as any increase in the number of role instances is proportional to an increase in the number of requests sent to Windows Azure Web services. Azure web services cannot process many requests at a time and throws the “Address already in use” exception. This could result in missing data points for several parameters.

You can use the _RoleInstanceCount parameter to obtain the number of role instances discovered by BMC PATROL for Windows Azure. For more information about this parameter, see the BMC PATROL for Windows Azure online Help.

Warning

Note

If you are monitoring a Windows Azure account having a large number of instances from a Linux agent, data collection might not happen properly. This is because a large number of files are open (Process handle count) with the collector Java process. The default limit for the number of open files in Linux environment is 1024. For successful data collection, increase the number to 2500 (when you are monitoring 5 Azure accounts, each account having 20 instances). Adjust this number as you increase the number of instances.

To check the limit on the number of open files on Linux, use the following command: ulimit -n

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Performance Manager for Platform as a Service 1.1