JDBC Type 4 Driver 2.0 Programmer's Reference (SQL/MX 2.x)

Chapter 7. Module File Caching (MFC)
Prev Next
Chapter 7. Module File Caching (MFC)
MFC Overview
Design of MFC
Configuring MFC
MFC Usage Scenarios
MFC Tuning Recommendations
MFC Limitations
Statement Caching
MFC Overview
The applications, which use JDBC T4 driver, face repeated SQL compiles while using prepared
statements. To overcome this issue, a driver side Most Frequently Used (MFU) cache is used. However,
the current design of the driver side cache consumes large amount of memory. The size of the
MXOSRVR process memory is directly proportional to the size of the driver side cache configured
through the maxStatements property. Higher maxStatements value (driver side cache size) can breach the
MXOSRVR process memory limit of 2 GB on the NonStop platform.
The Module File Caching (MFC) feature shares the prepared statement plans among the NonStop
SQL/MX database connections. The MFC helps in reducing the SQL compilation time during JDBC or
ODBC application's steady state, thereby reducing resource consumption.
Note: Module File Caching is supported only on systems running J06.07 and later J-series RVUs
and H06.18 and later H-series RVUs.
MFC Design
For information on the MFC design, see the HP NonStop SQL/MX Connectivity Service Manual.