Installation guide

CHAPTER 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1
What’s New 57
Flow control
When the server is very busy with many client connections, client request
threads may repeatedly conflict with each other for access to low-level system
resources. Flow control provides a coarser level of granularity for
synchronizing access to system resources by request threads. When enabled,
flow control can improve performance by replacing multiple, serial choke
points in the request processing sequence with a single choke point. Flow
control can be enabled separately for HTTP and IIOP clients. For more
information, see “Flow control” in Chapter 2, “Server Tuning,” in the
EAServer Performance and Tuning Guide.
Servlet buffer pool
Internally, EAServer uses 4K and 8K temporary buffers when assembling
servlet responses. EAServer 4.1.2 includes new server properties to tune the
size of the 4K and 8K internal buffer pools. For more information, see “Servlet
buffer pools” in Chapter 5, “Web Application Tuning,” in the EAServer
Performance and Tuning Guide.
Servlet Java cache
This new EAServer 4.1.2 feature allows caching of servlet output in Java core
memory, which offers a faster response than page caching for a limited class of
servlets. For more information, see “Understanding HTTP response caching
options” in Chapter 5, “Web Application Tuning,” in the EAServer
Performance and Tuning Guide.
Direct-access pseudocomponents
In EAServer 4.1.2, you can generate special stubs and skeletons that improve
the performance of pseudocomponent method calls. In a process called
marshalling, regular CORBA stubs convert parameter and return values to the
format required for IIOP network transport. Direct-access pseudocomponent
stubs and skeletons improve performance by eliminating the marshalling step.
For more information, see Chapter 34, “Creating and Using EAServer
Pseudocomponents,” in the EAServer Programmer’s Guide.