[GLLUG] Monitoring memory usage
Henrik Morsing
henrik at morsing.cc
Mon Nov 11 15:20:12 UTC 2024
On Wed, Oct 23, 2024 at 04:00:09PM +0100, James Dutton wrote:
>Hi,
>
>It is sometimes useful to monitor applications more than just the
>whole system totals.
>For example, Java programs have some good memory usage metrics.
>One can also aim to write programs slightly differently, such that
>they self limit their memory usage and trigger alarms when they are
>overloaded with work to do.
>So, instead of using too much memory, they instead limit the rate of
>requests they handle, thus limiting their memory usage.
>An application knows far more about its own behaviour than any
>monitoring tool, so having the application surface more useful metrics
>that the monitoring tool can read tends to work quite well.
>
>Kind Regards
>
>James
--
Apologies, have had some very busy weeks and forgot all about this discussion.
Our two main applications, SAP and Oracle, do this and it is monitored by their respective teams. The problem is that both are
internally limited (GAL in HANA, SGA in Oracle), so thing are not always transparent an DBAs often freak out when all they have to
do is increase their internat limits.
More information about the GLLUG
mailing list