![]() |
![]() |
|
|
Compressing Data Over a Network
The BEA Tuxedo system allows you to compress data being sent from one application process to another. Data compression is useful in most applications and is vital in supporting large configurations. You can use data compression when the sender and receiver of a message are on the same machine (local data compression), or when the sender and receiver of a message are on different machines (remote data compression). Both forms of compression provide advantages:
How to Set the Compression Level
If you decide to use data compression, you must set the CMPLIMIT parameter in the MACHINES section of the configuration file, as follows.
CMPLIMIT=string_value1[,string_value2]
The strings that make up the value of this parameter specify the threshold message size for messages bound to remote processes (string_value1) and local processes (string_value2). Only the first string is required. The default for both strings is the value of the MAXLONG parameter.
In addition, you have the option of setting the TMCMPPRFM parameter to establish an appropriate balance between compression and CPU performance. Higher and slower compression results in more efficient network bandwidth; lower but faster compression yields less CPU utilization.
To specify the desired level of compression, complete the following procedure.
A value of 1 specifies the lowest level of compression with the fastest performance; 9 represents the highest level of compression with the slowest performance. The lower the number, the more quickly the compression routine is executed.
For more information on setting the TMCMPPRFM variable, refer to tuxenv(5) in BEA Tuxedo File Formats and Data Descriptions Reference.
Selecting Data Compression Thresholds
You can designate a compression threshold for messages: any messages larger than the threshold you specify are compressed. To designate a compression threshold, set the CMPLIMIT parameter. For instructions, see How to Set the Compression Level.
When choosing data compression thresholds, keep in mind the following criteria:
For local data compression, you can assign a different threshold to each machine in an application. If this is the case, always choose the lowest limit possible for each machine.
Note: For high-traffic applications that involve a large volume of timeouts and discarding of messages due to IPC queue blocking, you may want to lower the demand of the application on the IPC queuing subsystem by having local compression done at all times.
Because compression depends on the type of data being transmitted, we strongly recommend that you try different settings in your environment to determine which one yields the best results.
See Also
![]() |
![]() |
![]() |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|