Skip to main content

Why does memory % differ for "show memory" and "show load" when using DataPower? - Middleware News


 The memory % in "show load" can be significantly higher than the memory % in "show memory". Why are they different? What do they mean?

Symptom

The WebSphere DataPower WebGUI status value "System Usage "(CLI command "show load") has a memory % that can be significantly higher than the status value "Memory Usage" (CLI command "show memory") memory %. What accounts for this discrepancy?

Cause

When you display "Memory Usage" from webGUI, notice the various categories of memory values:

The memory value in "Memory Usage" from the webGUI ("show memory" in CLI command) is based on Used Memory / Total Memory.

The memory value in System Usage from the webGUI ("show load" in CLI command) is derived by Requested Memory / calculated available Memory*. Note that Requested Memory is equal to Used Memory + Hold Memory.

In other words, System Usage takes into account all the memory that has been allocated from the Operating System (OS), regardless of whether it is being actively used, or simply held in reserve.
This is a useful number to note if you are looking at memory problems. However, the Memory Usage from webGUI ("show memory" in CLI command) figure would be a more accurate measure to use for capacity planning, since the Hold Memory is available to DataPower for re-use.

If you are looking for how much memory your traffic is currently using, look at Memory Usage from webGUI ("show memory" in CLI command).

Requested Memory is generally the highest amount of memory that has been Used and/or Held since the most recent reboot. When DataPower finishes with a block of memory, it returns that block to the Hold Memory list, not to the OS. So Requested Memory (Used Memory + Hold Memory) normally stays level or else grows. The Hold Memory is released back to the DataPower OS in case of an Out of Memory (OOM) condition, or a device reboot.

Resolving the problem

If your "show load" memory % is higher than your "show memory" %, that is because the latter does not include Hold Memory, a pool of allocated memory that DataPower has access to but is not currently using. In general, the "show memory" or Memory Usage % is a more accurate measure of the memory currently being used.
"show memory" = Used Memory / Total Memory
"show load" memory = Requested Memory / calculated available Memory*
Requested Memory = Used Memory + Hold Memory

* The calculated available Memory value varies but is approximately equal to 3 GB.

Comments

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w