|
|
tableBASE
DataKinetics tableBASE is a real-time in-memory table management solution that reduces mainframe resource usage, allowing for much faster applications, especially in transaction processing environments. A world-class table manager, tableBASE can lower your costs and mainframe TCO, dramatically reduce batch processing time and optimize your MIPS usage, offering dramatic performance benefits and more powerful and efficient applications.
Performance, Throughput and Capacity Improvements
|
|
tableBASE can dramatically improve the performance of DB2, VSAM or IMS systems. Performance increases of up to two orders of magnitude can be expected over existing I/O intensive DASD systems; an order of magnitude improvement over similar buffered DB2 or cached DB2 systems. Customers often can measure a 90% improvement in application run time.
For more information, see:
|
Figure 1: Performance Improvements |
|
Batch Capacity and Batch Window Performance Improvements
|
|
Batch processing is an important business function for most organizations in the financial services, credit, retail, and data processing industries. The amount of work needed to be done by batch programs is ever increasing, and there is constant pressure from 24x7 online transaction processing that competes for processing resources. Those organizations that must complete batch processing within a defined window are under extra pressure to complete that processing on time.
tableBASE is the perfect solution for organizations that need help with batch processing. Applications leveraging tableBASE can run 90% faster. Implementing tableBASE in many I/O-intense batch applications will definitely reduce the pressure.
For more information, see:
|
Figure 2: Improved batch performance |
|
Mainframe Cost Control
|
|
tableBASE can sharply reduce ongoing mainframe costs when those costs are related to MIPS usage and the corresponding MIPS licensing costs. With tableBASE, mainframe applications will use far fewer MIPS than they require now for their processing. This can lead to a direct savings of millions of dollars per year-money that can be reallocated to other IT projects-like your most important distributed system development projects, or your mainframe migration projects.
For more information see:
|
Figure 3: tableBASE cost savings |
|
Lower Cost Per Transaction
|
|
Banks and other financial institutions that process millions of transactions per day have intimate knowledge of their costs - they know the exact cost of their transactions- a significant portion of their ongoing operational expense (OpEx). Anything that can help reduce the cost per transaction has a direct and measurable positive impact on the bottom line.
In an environment in which system resource consumption is reduced, the cost-per-transaction experiences a parallel improvement. tableBASE sharply reduces the number of I/Os used by mainframe applications, reduces significantly the CPU cost associated with those I/Os, and reduces the number of MIPS required. In this way, tableBASE can reduce the cost per transaction in any I/O-intensive environment.
For more information, see:
|
Figure 4: Reduced cost per transaction |
|
MIPS Optimization
|
|
Most IT organizations that run mainframe systems are keenly aware of the cost of their MIPS (mainframe Millions of Instructions Per Second). Any increase in the number of mainframe applications, or any increase in the amount of mainframe processing necessitated by increased business needs, brings with it a demand for more MIPS. More MIPS translates directly into more money - money for new hardware and/or money for increased licensing fees.
DataKinetics MIPS Optimization allows mainframe applications to process at the same rate or higher, using far fewer MIPS. MIPS are not squandered; they are optimized. Fewer MIPS are needed for I/O, and more can be dedicated to actual processing. Implementing MIPS Optimization typically means that an IT organization will be able to increase mainframe capacity without spending money on new hardware, more MIPS or higher licensing fees.
For more information, see:
|
Figure 5: Reduced MIPS usage |
|
More Efficient Applications
|
|
tableBASE-powered applications are market-adaptive, growing and changing with the company as it grows and changes. They are as compatible with mergers and acquisitions as they are with divestitures. They are vital to business operations, and become an essential part of the company's value by enabling business top-line growth, while reducing costs.
Business Rules Optimization
Changes to business rules that take months to implement can now be managed in a day. And that is without a performance hit. Many other rules externalization solutions involve a serious performance hit-often including transferring information between applications, or requiring a great deal of I/O as part of the solution.
tableBASE allows for separation of business rules from applications, while retaining ultra-high-speed processing- without extra I/Os, without scrapping your existing applications, and without the need for new hardware.
Swap thousands of lines of If-Then logic from application code for a single call to an in-memory table.
For more information, see:
|
Figure 6: Efficient apps reduce maintenance costs |
|
Benchmark Results
|
|
DataKinetics commissioned IBM to run some tests comparing access rates of data in DB2 tables against data contained in in-memory tableBASE tables. After disappointing results, the IBM team buffered the data into memory, then buffered all of the data and the indexes.
The image to the right shows measured results of tableBASE v.s. buffered DB2. (The information was obtained at the IBM Benchmarking Center in Poughkeepsie, NY.)
Note that DB2 is a database, and tableBASE is not. tableBASE augments DB2, by making the most often accessed data available in optimized in-memory tables. In this way, applications are no longer delayed by I/O bottle-necks.
For more information, see:
|
Figure 7: Actual measured results vs. buffered DB2 |
|
How tableBASE Works
|
|
In many systems, applications fetch data from either a DB2 database, or a buffered DB2 database (see Fig 8, top). These systems access data either directly via I/O or from buffers, using the same path lengths as standard I/O.
In systems using tableBASE optimization, the DB2 database populates in-memory tables once. Application I/O calls are substituted with calls to memory-based tables (Fig 8, bottom).
This results in an improvement of from one to two orders of magnitude in application performance. Instead of fetching data at I/O speeds, or buffered I/O speeds, your applications now fetch data at memory speeds. Without buffering, without extra hardware.
For more information, see:
|
Figure 8: Above: Performance affected by I/O speed Below: Improvedments with memory speed |
|
Accessing tableBASE
|
tableBASE is accessed via its API-a single-call, and can be used in batch, CICS, IMS and other operating environments. You can retain your existing applications. All that's needed is a very small change (less than 1%) to your application code; simply change one or some of your SQL queries to tableBASE calls. Little or no knowledge of your application logic is required-no changes to application logic are required.
The resulting swap of I/O calls for in-memory tableBASE API calls helps you to obtain at least a 300% improvement in application performance.
For more information, see:
|
Related Products
|
tableBASE is DataKinetics flagship product; it is available as a stand-alone product, and is also a component of the turboTABLES product.
The following products complement tableBASE:
|
Read More
|
For further information about tableBASE and other DataKinetics products:
Download the tableBASE datasheet.
Download the Get More From Your Mainframe white paper to learn how tableBASE can help improve your mainframe performance and reduce your mainframe costs.
Read more about tableEXTENZ.
Read more about VTS.
|
|
|