Skip to Content

Dear LiveCache : What makes you so faster ?

Page 3 Personality :

LiveCache is one of the most talked about stuff in APO and what makes this darling so popular is its Lightning Speed..!!

It gets its Power and Speed with SAP In-Memory Computing concept.

SAP kicked off with SAP In-Memory Computing available in product form with the introduction of SAP Search

and Classification TREX ( Text Retrieval and Information Extraction ).

But today its very poorly utilized by LiveCache.

The Real Heroes :

Now, we will discuss about the features in LC ( LiveCache ), that contributes to this tremendous speed.

1. In-Memory Computing :

SAP handles the performance-critical application logic with LC. The relevant data is sent to LC and then kept in-memory.


In-memory computing allows the processing of enormous volumes of data in main memory to provide immediate results.

It minimize the movement of data within the database and between the database and the application,by keeping them in the global data cache of  the LiveCache.

The above fig. shows the approximate data transfer speed, based on the location data needs to travel

A. Data fetched from LiveCache and processed at Application Server, it takes approx. 1 ms

B. Data fetched from LiveCache and processed at LiveCache, it takes approx. 0.01 ms

C. Data fetched from Database Server and processed at Application Server, it takes approx. 10 ms

The above statistics clearly shows ” Data fetched from LiveCache and processed at LiveCache “, takes the least time and

that is what In-memory  computing does.

Here also, occasionally data may be moved to Disk when there is memory shortage in LC.

2. Object-oriented functions :

Uses of Object Oriented programming with the proper use of adequate C++ methods is also a remarkable reason behind LCs beauty.

LiveCache uses the persistent OMS (Object Management System) objects.

The C++ code running on the LC server provides extremely fast access to the objects in LiveCache memory and allows processing

load to be passed from the application server to the LiveCache server, rather than just accessing database data.

Details can be found here

    Concepts Used in Persistence – ABAP – Object Services – SAP Library

    Class Containers – SAP Documentation

3. Database procedure :

Database procedure ( also called Stored procedure ) are called from APO ABAP programs are executed directly in the SAP liveCache address space.

Since it runs in the address space of LiveCache , it is having direct access to OMS objects.

Now, the application data is completely available in main memory, this save a lot of effort and resource that would otherwise be needed for communication and the transfer of data.

Comments and Rectification :

Kindly put your comments, which can help me to further add values to blogs..!!

My mentors and guides over SDN, kindly rectify me if I am wrong somewhere..!!

Thanking You All..!!

You must be Logged on to comment or reply to a post.