on 08-22-2016 7:36 PM
What revision are you running?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is this constant or was it just during the time you executed the query. Can you also try querying the last 2 weeks of memory allocator use? My feeling is this is not the actual cause of the memory usage and may have only been for that moment and time when your queried it. Use the hana_memeory_history sql and do it for two weeks. This will allow you to see if this allocator has indeed grown and used more than normal.
Thank you Michael.
I was looking into the memory usage because I observed the following:
The indexserver has allocated most of the RAM (2TB), but the database is using around 1.4TB of it. Is there a way to release this space? I know there are blogs or notes saying it is normal to have indexserver allocate most of the space.
Mu doubt is with the system component using 795GB of space.
I have checked our other databases and system never used more than 250GB of space.
795GB seems like a memory leak.
Thanks,
Mrutyumjai
Can you show me the Memory allocator which are consuming the most memory? Use the memory overview query from note 1969700
Also to check if there is indeed a leak we need to see a rise in the allocator over a period of time. Again I will need you to check which allocator have risen over a 2 week period. Use the memory queries from note 1969700. You can change the time period in the modification section of the query
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.