wrapper.javaio.buffer_size |
||||||||
This property controls the size of the buffer used by the pipe between the JVM and Wrapper processes. When the JVM writes console output, the thread attempting to write will block if the pipe ever becomes full. This can lead to performance degradation in applications with lots of output. NOTEThe ability to set the pipe buffer size is currently not possible on Unix systems other than Linux. Windows All versions of the Wrapper prior to 3.5.21 used the system default buffer size which appears to be about 4KB on Windows. This was fine for most applications, however applications with very long lines of console output, or very large quantities of output would experience some performance degradation caused by blocking. Starting with Wrapper version 3.5.21, the default buffer size for Windows was set to 65536 (64KB), matching the typical default pipe capacity on Linux systems. This value will work for most applications and was chosen to avoid wasting too much memory when not needed. The buffer size can be set to any value between 4096 (4KB) and 10485760 (10MB). A value of "0" (zero) is also valid and tells the Wrapper to use the system default buffer size. Linux Starting with Wrapper version 3.7.4, this property is also supported on Linux systems. The maximum value for this property is the value of /proc/sys/fs/pipe-max-size. NOTEWrapper version 3.7.4 also introduces a change to how this property is handled: The property will be ignored if it is set to a value lower than the system's default pipe size (usually 4KB on Windows and 64KB on Linux). This ensures that deploying the same configuration on different systems will not inadvertently reduce the pipe size on systems whose default pipe size is larger than the configured value.
Other performance considerations
There is a lot of overhead by the system to render console log output. This is especially true on Windows.
If your application is experiencing performance issues logging large amounts of console output, we recommend either reducing the
log output or disabling the console log output by setting the wrapper.
Another way to improve performance is to increase the interval at which the buffered console output is processed by asking the Wrapper to use a dedicated thread.
See the wrapper. WARNINGAll Java output is sent across into own stdout/stderr pipes to the Wrapper process. If the Wrapper is slow writing to the console or file, then it will also slow down the ability to read output from the Java. If the pipe becomes full because the Wrapper has not read everything then the Java end of the pipe will block trying to write its output. This can have a performance impact on your application, and it is important to be aware of it. Any application will have this problem, including a standalone Java process.
You can alleviate this problem by enabling the wrapper. |
Reference: Console |
|









