NCMPBUF parameter: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 37: | Line 37: | ||
<ul> | <ul> | ||
<li>The [[Janus Web Server]] requests for which compression | <li>The [[Janus Web Server]] requests for which compression | ||
is requested (via the <var>[[COMPRESS | is requested (via the <var>[[COMPRESS (JANUS DEFINE parameter)|COMPRESS]]</var> setting on <var>JANUS DEFINE</var> or <var>JANUS WEB</var> commands, or via the <var>[[$Web_Set]]</var> function). | ||
<li>The <var>[[$Deflate]]</var>, <var>[[$Inflate]]</var>, <var>[[$Gzip]]</var>, and <var>[[$Gunzip]]</var> functions. | <li>The <var>[[$Deflate]]</var>, <var>[[$Inflate]]</var>, <var>[[$Gzip]]</var>, and <var>[[$Gunzip]]</var> functions. | ||
Revision as of 01:08, 10 October 2014
Number of compression buffers
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- User 0 CCAIN parameters
- Related products
- All
- Introduced
- Before Sirius Mods 6.7
Description
This numeric parameter indicates the number of compression buffers to be allocated at initialization. It must have a value between 0 and 32767.
Since datastream compression and decompression requires a compression buffer, this parameter limits the number of simultaneous compression or decompression operations. If not set, no buffers are allocated and no compression or decompression is allowed. If all compression buffers are in use, a compression or decompression request waits for the next available buffer.
Since decompression and (especially) compression are very CPU-intensive operations, there is probably little benefit to having many such operations running at once. Adding to this the fact that compression buffers are quite large (over 300K bytes), suggests that it is best to use a relatively small value for NCMPBUF (like 10 or less).
Compression and decompression are used by: