Totalview® for HPC User Guide : PART VI Appendices : Appendix C Resources
Appendix C Resources
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.
NOTE >> 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.
The basic differences are:
TotalView
Team & Enterprise
TotalView
Individual
Comment
Execute on any licensed computer of the same architecture
Node locked.
You can execute TotalView Individual only on the computer you install it on.
Number of users is determined by license
Only one user
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 32 processes and threads.
 
Your license determines the number of processors upon which your program can run.
 
A program can execute on no more than 16 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.
Memory debugging is bundled.
No memory debugging
 
TotalView Documentation
The following table describes all available TotalView documentation:
 
Product
Title
Description
HTML
PDF
Print
General TotalView Documentation
 
Getting Started with TotalView Products
Introduces the basic features of TotalView, MemoryScape, and ReplayEngine, with links for more detailed information
x
x
 
 
TotalView Platforms Guide
Specifies supported platforms for TotalView, MemoryScape, and ReplayEngine
x
x
 
 
TotalView Evaluation Guide
Brochure that introduces basic TotalView features
 
x
x
User Guides
 
 
 
 
 
 
TotalView User Guide
Primary resource for information on using the TotalView GUI and the CLI
x
x
 
 
Debugging Memory Problems
with MemoryScape
How to debug memory issues, relevant to both TotalView and the MemoryScape standalone product
x
x
 
 
Reverse Debugging with Replay Engine
How to perform reverse debugging using the embedded add-on
ReplayEngine
x
x
 
Reference Guides
 
 
 
 
 
TotalView Reference Guide
A reference of CLI commands, how to run TotalView, and platform-specific detail
x
x
 
New Features
New features in the current release
 
 
 
 
What’s new in this release
On the landing page of the HTML documentation, lists new features for the documented release
x
 
 
 
TotalView Change Log
Details the changes to the product from release to release
x
x
 
Installation Guides
 
 
 
 
 
TotalView Install Guide
Installing TotalView and the FLEXlm license manager
x
x
 
 
MemoryScape Install Guide
Installing MemoryScape as a standalone product
x
x
 
In-Product Help
Help screens launched from within the product’s GUI
 
 
 
 
TotalView Help
Context-sensitive help launched from TotalView
x
 
 
 
MemoryScape Help
Context-sensitive help launched from MemoryScape
x