When to use shared memory objects?

alejiandro_sensejl — Mon, 04 Oct 2010 21:30:05 GMT

Hello everyone,

today I've used shared memory objects for the first time (on a small (<200 records) customizing table). I just wanted to try this, so I'm sure this isn't a real scenario for these. I think I've understand the technical concept behind these, but I'm not sure how I can push this technology to its limit.

I hope you can give me some examples when / for what data I should use a shared memory object ...

Thanks in advance and best regards,

Alej

Re: When to use shared memory objects?

SuhaSaha — Tue, 05 Oct 2010 02:34:34 GMT

Hello Alej,

I don't think that you should decide which data cluster(viz., SAP Memory, ABAP Memory etc.) to use the "type" of data. Rather the decision is done based on the "size" of the data & the scenario where you want to use it.

As a thumb rule if you want your data across "multiple-user" sessions(SAP Memory scope is across all the sessions of a user) you go for SHM concepts.

But bear in mind SHM is app server specific. Suppose you've multiple app servers in you PROD(in almost all the projects i've been part of have multiple app servers in the PROD) & there is a high probability that the users are logged in different App Server. In this case SHM won't be useful.

Hope i'm clear in my explanation.

BR,

Suhas

topic Re: When to use shared memory objects? in Application Development and Automation Discussions

When to use shared memory objects?

Re: When to use shared memory objects?