ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanislav Lukyanov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-11533) Improve memory usage reporting in the logs
Date Tue, 12 Mar 2019 11:40:00 GMT
Stanislav Lukyanov created IGNITE-11533:
-------------------------------------------

             Summary: Improve memory usage reporting in the logs
                 Key: IGNITE-11533
                 URL: https://issues.apache.org/jira/browse/IGNITE-11533
             Project: Ignite
          Issue Type: Improvement
            Reporter: Stanislav Lukyanov


Currently node's memory usage is reported in the log like this
{code}
    ^-- PageMemory [pages=66407]
    ^-- Heap [used=303MB, free=91,6%, comm=849MB]
    ^-- Off-heap [used=260MB, free=62,73%, comm=580MB]
    ^--   sysMemPlc region [used=0MB, free=99,21%, comm=40MB]
    ^--   TxLog region [used=0MB, free=100%, comm=40MB]
    ^--   Default_Region region [used=260MB, free=47,97%, comm=500MB]
{code}
And it also used to report "Non heap" metrics which were removed in IGNITE-9305.

This has several issues
1. "PageMemory" line alone doesn't help to understand the Ignite off-heap memory usage - page
size is needed to calculated the used size, and maxSize of the data regions are needed to
calculate the amount of the memory left.
2. "Non heap" could actually be useful. The line used to show "free=-1%" in most setups. This
is because metaspace pool of the JVM is not limited by default which makes the total size
unlimited. In general, it would be good to see distribution among the non-heap pools (metaspace,
direct buffers) to be able to tune JVM settings accordingly.

Let's do the following:
- Don't print "PageMemory" line - it's cryptic and adds little value to the "Off-heap" section
- Bring "Non heap" back in some way
-- Don't print "free=-1%" - either print "N/A" or don't print "free" at all
-- Add a suggestion to limit metaspace (same as we do for direct memory) - which will enable
correct "free" calculation
-- Look into possibility of showing distinct metrics for direct memory and metaspace, so that
the user can tell which to tune



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message