TotalView Debugger Team License

TotalView Team lets you debug multiprocess, multithreaded programs on a wide, diverse range of computers ranging from laptops to supercomputers.

Note: TotalView Team and TotalView Enterprise have exactly the same features. The differences between them are the resources available while debugging. For more information, see the TotalView Enterprise licensing page and our comparisons page. In general, all TotalView features you see described on our web site are part of TotalView Team .

TotalView Team use is constrained by the number of licensed tokens. (We will have worked with you to determine how many tokens you need.) For example, if you have 10 developers and each is debugging 16-process jobs, you should have 160 tokens.

TotalView Team doesn't care how many users are debugging at the same time. So, for example, if you have 40 developers, each could debug a four-process program at the same time. Or, if you need to debug at a higher scale, a developer could debug a 128-process job, which would leave 32 unused tokens for other developers. The following figure shows three developers. The objects within the bucket are tokens; 12 tokens are available.

A developer begins debugging a one-process job. 11 tokens remain.

The job becomes bigger as it starts 9 more processes. TotalView takes 9 more tokens; two tokens remain for other developers.

In the next figure, two developers are debugging. One is debugging a 2-process job and the other is debugging a 6-process job. 4 tokens are left. These tokens can be used by another developer or they can be acquired by either of the developers if their jobs spawn more processes.

The second developer's progrm spawns four more processes and takes the four remaining tokens.

A third developer starts TotalView Team. Since there are no tokens left, the developer is told that no more tokens are available—this third developer must wait until one of the other developers exits from TotalView Team.

Notice that while tokens limit usage, tokens also give you considerable flexibility. At one extreme, one developer can use all of the tokens. At the other, each of your developers could be using a single token. Unlike TotalView Individual, TotalView Team does not track the threads being debugged.

Changing Licenses Within a Session

When writing multiprocess, multithreaded programs, testing and debugging most often begins at low-scale and then moves to larger machines where it can be tested and debugged using more processes and threads. If your organization purchases more than one product from the TotalView family—for example, you have access to TotalView Individual and TotalView Team—TotalView can transparently shift from TotalView Individual to TotalView Team as the scale at which you are debugging changes. For example, if you need more than 16 processes, TotalView will locate the TotalView Team license.