Maestro Server Classes and Their Definitions

There are two classes of Maestro servers, "General" and "Load".

The only difference in behavior between the two is that a Load server will only play one Composition at a time. It will refuse to play another one if it already has one. It can play multiple Tracks from the same Composition, if the Tracks are set up that way, but it cannot mix Tracks from multiple different Compositions.

CloudTest's deployment tools (such as Grids, etc) typically set all environments to have one General server on the main instance, and all others to be Load servers. This is not required and users with adequate permissions wishing to change this can use the Central < Server List and change any Maestro to be whichever type is preferred.

Users comparing options in the Composition Editor > Track, Location drop-down should keep the following in mind when selectng distribution options for a given Track:

  • If a Track can play on "Any server", it can play on any server. It cannot play on a Load server that has some other Composition already playing, but it could play on any Load server that the Composition it is within is using.
  • Similarly , "Any general server" means what it says—any server of type General, regardless of what else might be happening on that server.
  • "Any load server" means it can play on server of type Load. It cannot play on a Load server that has some other Composition already playing, but it could play on any Load server that the Composition it is within is using.
  • "Dedicated load server" means the Track must play on a Load server all by itself. It won't play on a General server and it won't play on any Load server that already has some other Track on it. This is the most commonly used setting for Load tests, for obvious reasons.
Note: Tracks can also be directed to specific servers or locations, sometimes in conjunction with the above, for example "any load server in location x".

CloudTest doesn't provide"load balancing" features in separation from these selections, nor does it attempt to "use all servers" or "evenly spread across servers" or similar propositions.

For example, by setting several Tracks in a Composition to "any Load server", then they will likely all go onto the same Load server, because that's what you said for each Track — any Load server will do. On the other hand, if you said "any dedicated Load server", then they will each go on to separate Load servers.

There is curently no way to arbitrarily group Tracks, such as "put these 3 Tracks together on a single Load server, and these 4 other Tracks together on a different Load Server", unless you can do that through the use of Locations. If you need to do something that specific, then you will need to assign the Tracks to specific servers manually.

The "Distributions" U/I allows a Track to be distributed as above, but in multiple ways simultaneously. For example, if a user wants one copy on a dedicated load server in location A and another copy on a dedicated load server in location B.