Performance issues experienced when over-taxing the local TSR

In some instances, as demand for data access increases, and tableBASE usage increases, customers can experience increased performance issues both at initialization, and during run-time. Consider the scenario below, where a large number of tables are loaded into a single TSR from multiple libraries.

Performance issues at initialization
Figure 71. Performance issues at initialization

At initialization, data is loaded from tableBASE libraries into the local TSR row-by-row, with associated indexes being constructed for each table. This is a very I/O intensive process, and can be a quite time-consuming, particularly if there are a large number of tables being loaded from a large number of libraries, as is the case here.

The situation can be made worse if another set of tables has to be loaded after the first set. The sequential nature of loading significantly delays the application for the entire duration.

During run time, access congestion can be an ongoing performance issue, especially if the local TSR is burdened with many tables (access is not efficient if a TSR contains many tables).

Performance issues at run-time
Figure 72. Performance issues at run-time

DataKinetics VTS product, an in-memory data-sharing performance-enhancement product which augments the tableBASE core product, is the solution for both initialization and run-time performance degradation.