topic Shared Memory Concept? in Application Development and Automation Discussions

Shared Memory Concept?

former_member282589 — Mon, 04 Nov 2019 23:43:04 GMT

I'm currently trying to find a way to increase speed to current report, so I'm trying various way.

'Shared memory objects are ABAP Object Instances, which can be stored in the shared memory area on an application server. Instead of going to the database to retrieve the required data, the data is accessed through the shared memory, thereby providing faster data retrieval.'

So..When I'm running same report, and If I'm using different WPs in this report, BAPI COMMIT works like I'm working with 1 WP?. Like this :

It's just an idea. So many help will be appreciated.

Re: Shared Memory Concept?

FredericGirod — Tue, 05 Nov 2019 06:45:09 GMT

if you want to improve perfomance, first kill this "Wait Until"

If you work only in your LUW, forget Shared memory, and have a look to Design Pattern Singleton or Multiton

Re: Shared Memory Concept?

Sandra_Rossi — Tue, 05 Nov 2019 08:23:01 GMT

You can commit or rollback only the updates which are done in the same LUW.

Each workprocess has its own LUW. It means that you must call BAPI_TRANSACTION_COMMIT (or rollback) in each workprocess.