Another set of important parameters available through the P6 Compression Server Administrator Application is the set of parameters controlling P6 Compression Server performance. In most situations, the default settings are enough.
To review and modify P6 Compression Server configurations:
The following table summarizes the Compression Server node settings:
Variable Name | Value | Min | Max | Tool tip |
---|---|---|---|---|
|
|
|
| Telemetry user name. |
|
|
|
| Telemetry password. |
|
|
|
| Port value for P6 Professional. |
|
|
|
| Scheduling delay of a compression job. For networks with high latency (>250ms) if using huge compression buffers (>512KB) a job delay might be acceptable in order to speed-up jobs that return a lot of Blob data. |
|
|
|
|
Size of the main compression buffer. The larger the buffer, the better the compression ratio. For 2GIPS computers, compression speed is 1KB/ms. Each compression job uses memory up to 12 times the size of the main compression buffer. |
|
|
|
| The socket send buffer size for P6 Professional client connection. |
|
|
|
| Number of rows in a database data block. |
|
|
|
| Maximum time allowed for a job to complete. |
|
|
|
| Maximum time allowed for a compression task to complete. A job consists of one or more compression tasks. |
|
|
|
| When CPU goes beyond 95% the thread pool might respond with 25ms to 600ms latency. This can have a negative impact on performance. Creating and garbage-collecting threads can provide better performance on Windows computers in this case. |
|
|
|
| |
|
|
|
| Socket linger time. |
|
|
|
| The Timeout interval for an inactive session that has a pending database transaction. |
|
|
|
| The Timeout interval for an inactive session. |
From a performance tuning standpoint, the Threadpool folder of the Primavera P6 Configuration folder would be of interest.
From a debugging standpoint, the SeverityLevel field of the Log/File Logger folder would be of interest. (The default is error. Setting SeverityLevel to debug makes the log very verbose.)
Legal Notices
Copyright © 2005, 2017,
Oracle and/or its affiliates. All rights reserved.
Last Published Tuesday, February 21, 2017