#Caché

Introduction

To overcome the performance limitations of traditional relational databases, applications - ranging from those running on a single machine to large, interconnected grids - often use in-memory databases to accelerate data access. While in-memory databases and caching products increase throughput, they suffer from a number of limitations including lack of support for large data sets, excessive hardware requirements, and limits on scalability.

Abstract

In a recent benchmark test of an application based on InterSystems Caché, a sustainable rate of 8.9million database accesses/second, with peaks of 16.9 million database accesses/second, was achieved. These results were from a test performed on a connected system of eight applications servers, using Intel Xeon 5570 processors, and running Linux as the operating system. This benchmark shows that:

InterSystems has implemented a broad set of MultiValue extensions for its Caché multidimensional database. These extensions enable the migration of MultiValue applications to Caché and bring the full range of Caché object and SQL development technologies to MultiValue developers. The result: your existing MultiValue investments are preserved, you gain a broad spectrum of highly scalable deployment options, and your developers can combine the best of MultiValue, object, relational, and technologies to extend existing applications and build new ones.

Executive Summary

The best way to compare the performance of database products is in a head-to-head test using a real application, preferably one of your own. This is especially true when evaluating Caché's post-relational technology, because "standard" transaction processing benchmarking methodologies assume the restrictive "row and columns" format of a relational database. They cannot accurately predict the performance of real applications, which often use complex data models.

Abstract

A benchmark of a real-world application, which loads data into a data warehouse for subsequent analysis, was performed. To conduct the benchmark, one module of the Oracle-based application was replicated in Caché ObjectScript. Only about 40 person-hours of work was required to duplicate the functionality of the original module in Caché.