The THREAD compiler option enables the COBOL program for execution in a Language Environment
enclave with multiple POSIX threads or PL/I tasks.
A program compiled with the THREAD compiler option can also run in a non-threaded environment, however there will be some degradation in the initialization and termination of the COBOL program due to the overhead of serialization logic that is done for these programs.
The THREAD compiler option also requires the use of the IS RECURSIVE clause on the PROGRAM-ID statement.
Performance considerations using THREAD (measuring CALL overhead only):
One testcase (Assembler calling COBOL) using THREAD was 35% slower than using NOTHREAD.
One testcase (COBOL statically calling COBOL) using THREAD was 30% slower than using NOTHREAD.
One testcase (COBOL dynamically calling COBOL) using THREAD was 30% slower than using NOTHREAD.
A program compiled with the THREAD compiler option can also run in a non-threaded environment, however there will be some degradation in the initialization and termination of the COBOL program due to the overhead of serialization logic that is done for these programs.
The THREAD compiler option also requires the use of the IS RECURSIVE clause on the PROGRAM-ID statement.
Performance considerations using THREAD (measuring CALL overhead only):
One testcase (Assembler calling COBOL) using THREAD was 35% slower than using NOTHREAD.
One testcase (COBOL statically calling COBOL) using THREAD was 30% slower than using NOTHREAD.
One testcase (COBOL dynamically calling COBOL) using THREAD was 30% slower than using NOTHREAD.
No comments:
Post a Comment