SymXchange API

Memory Configuration

Memory Configuration

This section provides information related to SymXchange’s memory need. You can reference this information to evaluate the memory needs of a credit union’s SymXchange deployment.

Credit union members access their accounts directly from their smartphone or tablet apps. Initially, the app makes requests to SymXchange to locate the member’s account, and retrieves basic personal and account information (description, balance, pending ACHs and holds, shares, and loans) to display in the account landing page. The user can then navigate to select a particular share or loan to view further details (share maturity date, loan next payment date, transaction histories, etc.). Typically, each request from the mobile app to SymXchange retrieves sufficient data to display for one app screen. Hence, the amount of data transferred is relatively small.

A load test was conducted to observe SymXchange’s performance under a load of 100 program threads making concurrent requests to SymXchange services. The use of program threads does not accurately translate to the simulation of human users using the system because with real human users there is more idle time between request calls. It was observed that the number of WSDLs published does not significantly impact the run time memory usage. Memory profiling of SymXchange showed that it could adequately handle the load subjected.

SymXchange performed well under the load test using the hardware and software configurations described below.

Reference Implementation Hardware Resources

  • 6 CPUs
  • CPU clock speed: 4116 MHz
  • RAM size: 36,864 MB
  • Paging Space: 4096 MB

Reference Implementation Software Memory Specifications

  • Maximum heap size: 5120
  • Minimum heap size: 2048
Last updated Fri Mar 3 2023