Object Code Accelerator Manual

Introduction

Object Code Accelerator Manual—528144-003

1-3

OCA Translation Mode

You explicitly accelerate your TNS program as part of the build or install process.When

you explicitly accelerate your program in this way, you are immediately alerted of any

error conditions.

If you do not want to accelerate a TNS object file, you can use the Binder CHANGE

OCA ENABLE OFF command to disable inadvertent acceleration. See OCA and

Binder on page 6-1 for further information about Binder commands that work with OCA

and the Binder Manual.

Usage Consideration

•

If a program calls a user library and that library is not already accelerated,

procedures in that library execute in TNS mode.

OCA Resource Requirements

OCA, like an optimizing compiler, is both CPU-intensive and memory-intensive. Try to

run OCA on a lightly loaded processor with more than 16MB of physical memory. OCA

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 OCA. 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-3 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-3. Comparing TNS and Accelerated Object File Sizes Without a

Symbols Region

TNS Object Code

Binder Region

Accelerated

Object Code

VST0103.vdd