MapGuide RFC 87 - SiteInformation enhancements

This page contains a change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.

Status

RFC Template Version	(1.0)
Submission Date	Oct. 01, 2009
Last Modified	(Bruce Dechant) Timestamp
Author	(Bruce Dechant)
RFC Status	draft
Implementation Status	(pending)
Proposed Milestone	(2.2)
Assigned PSC guide(s)	(Tom Fukushima)
Voting History	October ??, 2009
+1
+0
-0
-1
no vote

Overview

This proposal is to add additional memory statistics to the SiteInformation schema.

Motivation

When running stress tests on the server or just quering the current state of the server it would be nice to know the current working set memory and the virtual memory being used by the server.

Proposed Solution

A new SiteInformation schema will be added with the following new statistics:

WorkingSet
VirtualMemory

The new SiteInformation schema version will be SiteInformation-2.2.0.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
  <xs:element name="SiteInformation">
    <xs:annotation>
      <xs:documentation>Site Information</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:sequence>
        <xs:element name="SiteServer">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="DisplayName" type="xs:string"/>
              <xs:element name="Status" type="xs:string"/>
              <xs:element name="Version" type="xs:string"/>
              <xs:element name="OperatingSystem">
                <xs:complexType>
                  <xs:sequence>
                    <xs:element name="AvailablePhysicalMemory" type="xs:integer"/>
                    <xs:element name="TotalPhysicalMemory" type="xs:integer"/>
                    <xs:element name="AvailableVirtualMemory" type="xs:integer"/>
                    <xs:element name="TotalVirtualMemory" type="xs:integer"/>
                    <xs:element name="Version" type="xs:string"/>
                  </xs:sequence>
                </xs:complexType>
              </xs:element>
            </xs:sequence>
          </xs:complexType>
        </xs:element>
        <xs:element name="Statistics">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="AdminOperationsQueueCount" type="xs:integer"/>
              <xs:element name="ClientOperationsQueueCount" type="xs:integer"/>
              <xs:element name="SiteOperationsQueueCount" type="xs:integer"/>
              <xs:element name="AverageOperationTime" type="xs:integer"/>
              <xs:element name="CpuUtilization" type="xs:integer"/>
              <xs:element name="WorkingSet" type="xs:integer"/>
              <xs:element name="VirtualMemory" type="xs:integer"/>
              <xs:element name="TotalOperationTime" type="xs:integer"/>
              <xs:element name="ActiveConnections" type="xs:integer"/>
              <xs:element name="TotalConnections" type="xs:integer"/>
              <xs:element name="TotalOperationsProcessed" type="xs:integer"/>
              <xs:element name="TotalOperationsReceived" type="xs:integer"/>
              <xs:element name="Uptime" type="xs:integer"/>
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
</xs:schema>

Implications

This is new schema only. There will be no effect on existing applications. However, in order to get the new schema you must use the new version when doing the request.

Test Plan

Check that new schema returns new information.

Funding/Resources

Supplied by Autodesk.