Accelerator Manual (G06.24+, H06.03+)

Introduction

Accelerator Manual—527303-002

1-4

Accelerator Resource Requirements

The Accelerator, like an optimizing compiler, is both CPU-intensive and memory-

intensive. Try to run the Accelerator on a lightly loaded processor with more than 16MB

of physical memory. The Accelerator uses large amounts of the extended segment

heap area (about 135 KB per 1000 TNS instructions). Much of this virtual memory

must remain in physical memory to avoid page faults that slow the Accelerator.

Accelerating large programs on processors with less than 16MB of physical memory

can lead to unacceptable performance.

Accelerated object files require more disk space and memory space than TNS object

files. Figure 1-3, Comparing TNS and Accelerated Object File Sizes Without a Symbols

Region, on page 1-4 shows that an accelerated object file, without a symbols region,

requires about twice as much disk storage space as the corresponding TNS object file.

Figure 1-4, Comparing TNS and Accelerated Object Files Sizes With a Symbols

Region, on page 1-5 shows that an accelerated object file, with a symbols region,

requires about 25 percent more disk storage space than the corresponding TNS object

file. You can strip the symbols region from the accelerated program without affecting

performance. However, accelerate the TNS object file with the symbols region and

then strip the symbols region. The Accelerator produces more efficient code from

source TNS object files that contain a symbols region than those without the region.

Figure 1-3. Comparing TNS and Accelerated Object File Sizes Without a

Symbols Region

TNS Object Code

Binder Region

Accelerated

Object Code

VST0103.vdd