Abstract: Registering a client with a distributed service. A method may be practiced, for example, in a network computing environment including a client at a local site and a number of distributed services at a number of remote sites. The method includes pinging one or more distributed services at one or more remote sites. A message is received from a distributed service from among the one or more distributed services. The message specifies an optimal remote site. The method further includes registering with a distributed service at the optimal remote site.

Abstract: A new schema implementation enables reversible changes to be made to definitions in a schema. The definitions of attributes and classes are in the form of schema objects. Each schema object has an internal ID in addition to its unique name and object ID (DID), and a deactivation flag for indicating whether the schema object has been deactivated. To modify an attribute or class, the corresponding schema object is deactivated by setting its deactivation flag to “TRUE,” and a new schema object is created to contain the changes. The new schema object has the same unique name and DID as the old schema object but is given a different internal ID. When a client wants to access instances of the schema object by its unique name or DID, a translation is made to provide the internal ID of the new schema object such that instances of the new schema object are located instead of the old schema object.

Abstract: An improved scalability testing architecture for distributed applications allows testing of scalability with respect to a given number of computers using a test network having only a small fraction of that number of computers. Each client computer in the test network hosts multiple bootable systems in bootable partitions which timeshare the host machine on a mutually exclusive basis. A launcher in each bootable system verifies scheduling information for an instance of an application under test residing in the same partition and either permits or prevents continued operation of the instance based on the scheduling information. If continued operation is to be prevented, the launcher triggers a boot next routine to exit and cede control of the computer to the next bootable system on the computer.

Abstract: Disclosed herein is a method and apparatus for measuring central processing unit (CPU) usage required to execute a predetermined workload that includes system overhead usage of the CPU as well as direct usage of the CPU. The CPU is driven to run processing cycles to perform a workload task or to perform a CPU bound task. The CPU bound task is a cycle soaker; a cycle soaker task runs directly on the CPU and has no system overhead. The cycle soaker task runs whenever there is no workload task ready to run. A monitor module measures the total of all cycles run by the central processing unit from beginning to end of execution of the workload and measures the soaker cycles run by the CPU from beginning to end of execution of the workload. CPU usage attributable to the workload is measured by deducting the soaker cycles from the total of all cycles.