TotalView Family Differences
This manual describes the TotalView Enterprise, TotalView Team, and TotalView Individual debuggers. Each of these supports the use of the CLI debugger as well. In all cases, TotalView Enterprise and TotalView Team have the same features, differing only in the way they are licensed. TotalView Individual differs in its feature set.
|
The most fundamental differences between TotalView Team and TotalView Enterprise are the way resources are shared and used. When you purchase TotalView Team, you are purchasing “tokens.” These tokens represent debugging capabilities. For example, if you have 64 tokens available, 64 programmers could be active, each debugging a one-process job; or two programmers, each debugging a 32-process job. In contrast, a TotalView Enterprise license is based on the number of users and the number of licensed processors. You’ll find more precise information on our web site.
|
|
TotalView
Team & Enterprise |
TotalView
Individual |
|
|
Execute on any licensed computer of the same architecture
|
You can execute TotalView Individual only on the computer you install it on.
|
|
|
Number of users is determined by license
|
The TotalView Enterprise license limits the number of users. TotalView Team does not.
|
|
|
Number of processes limited by license. No limit on threads
|
No more than 16 processes and threads.
|
|
|
Your license determines the number of processors upon which your program can run.
|
A program can execute on no more than two cores.
|
TotalView Enterprise licenses the full capabilities of all machines upon which it runs. TotalView Team can acquire part of your machine.
|
|
Processes can execute on any computers in the same network.
|
Remote processes are not allowed.
|
Processes must execute on the installed computer.
|
|
Remote X Server connections allowed.
|
No remote X Server connections are allowed.
|
Programmers cannot remotely log into a computer and then execute TotalView Individual.
|