How does Reporter 9 calculate available memory?



Where does the declared available memory, called "capacity" come from, in Reporter 9?

Using the Windows Diagnostic utility, "winmsd" we see a discrepancy between "Total Physical Memory" and the value Reporter declares as memory Capacity.  What value is Reporter using?

Using the LINUX command "ps aux | grep bcreport" I see a percentage value for capacity that is smaller than that reported by Reporter.


There are two locations, in the Reporter User interface, where we declare how much memory we believe is available for us to use. 

Here's how to find both of them:

  • Log into Reporter, using the admin account.
  • Navigate to the Administration section.
  • Click General settings > Reporter settings <system settings > Alerts settings.
  • The value reported, as "capacity" here, is the value reporter declares as available memory.
  • Clicking on the system Overview > Diagnostics also shows this same value.

NOTE 1: The equivalent value, when you run the Microsoft "winmsd" application, is called Available Virtual Memory.  In other words, we are not the same value as  the "Total Physical Memory" value.

NOTE 2: For both LINUX and WIndows, Reporter will only show the capacity, as a percentage of the Virtual memory.

NOTE 3: The linux command   " ps aux | grep bcreport" will report a smaller percentage than Reporter because it only uses physical memory as its total value.   The two examples below show the LINUX PS command reporting a memory capacity of 14975988 wirth Reporter showing a total memory of 20.46 GB.

  • The command and its output looked like this:

[root@userX  Reporterserver]# ps aux | grep bcreport


root      3726  8.1 58.8 14975988 9597616 ?    Ssl  13:35   8:49 /DATA/Reporter9/bcreporter --service

[root@n1cr02 Reporter9]#

  • While the Reporter UI looked like this:


The same type of information is contained in the sysinfo file, provided by Reporter Diagnositics.  The value of virtual memory is called Page File: Max Size. See bellow, for an example: 
Host Name:                 Nameofserver-REPORTER
OS Name:                   Microsoftr Windows Serverr 2008 Standard
OS Version:                6.0.6002 Service Pack 2 Build 6002
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:  
Product ID:                55041-339-1752571-76391
Original Install Date:     11/20/2009, 6:41:46 AM
System Boot Time:          1/11/2010, 4:55:32 PM
System Manufacturer:       IBM
System Model:              IBM System x3650 -[7979IXT]-
System Type:               x64-based PC
Processor(s):              2 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 23 Stepping 10 GenuineIntel ~1992 Mhz
                           [02]: Intel64 Family 6 Model 23 Stepping 10 GenuineIntel ~1992 Mhz
BIOS Version:              IBM -[GGE144AUS-1.15]-, 4/3/2009
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (GMT+08:00) Taipei
Total Physical Memory:     8,190 MB
Available Physical Memory: 6,653 MB
Page File: Max Size:       16,432 MB
Page File: Available:      15,038 MB
Page File: In Use:         1,394 MB

NOTE 1:  For best practices information on Reporter see  000008247

NOTE 2:  The above triggers are for general out-of-memory conditions that occur while the database is loaded , however available memory ius also checked prior to running reports, For details on how the required memory needed to run reports is calculated, please see 000015704

Additional Information
Bug Number
InQuira Doc IdKB3655

Article Feedback

Did this Article solve your issue?
Additional Comments:
Previous MonthNext Month