Skip to Content

Memory consumption of BSP-application

Is there a tool to see how much memory a BSP-application uses on the application server?

Or even better how the memory consumption changes during requests?

The system i'm on is a WAS6.20.

I browsed a lot of docu already but when it comes to memory consumption i only found ways to display the size of objects in the ABAP debugger. But i am more interested on the memory consumption in relation to the time the application is running (e.g. to see what memory the session takes in a stateful application etc.).

Martin

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Aug 19, 2005 at 10:03 AM

    Sure - use the memory inspector. Just set breakpoints where you want to take your memory snapshots. Once in the debugger, choose Development->Memory Analysis->Create Memory Snapshot.

    Once done with your snapshots, from the SAPGui you can call Tcode S_MEMORY_INSPECTOR.

    This gives you a huge amount of detail as to where you memory is allocated. You can do deltas between different snap shots as well.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 19, 2005 at 10:03 AM

    Hi Martin,

    by using the transaction sm04 you can see how much memory a stateful session uses. Perhaps somebody knows a better solution. Did you take a look at the transaction smicm? It has lots of statistics perhaps you can find something useful.

    regards

    Thomas

    (Thomas Jung was faster - again)

    Message was edited by: Thomas Ritter

    Add a comment
    10|10000 characters needed characters exceeded

    • >That rules out stateful applications for 500+ concurrent users

      That's why it is nice that BSP supports stateless as well. I have an application that has about 2500+ concurrent users and I had to go with a stateless MVC approach. I swap my model object to disk by serializing it to XML. There are several weblogs on SDN about the topic.

      On the other hand don't underestimate how many concurrent stateful sessions you can have. Even an application with a lot of internal tables, doesn't have a session size that grows that much. With efficient programming I am able to handle large datasets and keep my session footprint at about 2-3Mb. Also SAP does a good job of swapping contexts out of main memory as they become older. Therefore I am able to have applications that support a few hundred concurrent users in stateful mode with only 5Gig of main memory on my production box.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.