Is there a default maximum memory allocation ?

Hi,
I would like to ask if there is a default maximum memory allocation in the virtual machine?
I know there are params for setting the initial und maximum size but I'm not sure if the vm will take as much memory as I have in my computer or not.
thanks
guenter

Hi guenter
Are you looking for the -Xmx parameter?
According to the below link, the default maximum is 64MB
http://java.sun.com/products/hotspot/2.0/README.html#Xmx
tsopa

Similar Messages

  • Is there a maximum memory allocated?

    Dear all,
    Anyone knows if there's a limitation to the maximum memory
    that labview can allocate in Win98?
    I cannot allocate more than ~ 19500 KB and my computer has
    1GB.
    Cheers,
    Ernest

    It seems it is a problem with the working set size and locking of pages. We have developed under Win2000 and have a double buffer daq application. The problem was the application was too late in the loop to get the data from the driver so it gets overwritten. Think of calling AI Read in a loop and the loop stopped for some time.
    I suppose you have no documentation for the windows API so I give you some from the MSDN.
    VirtualLock is the function which locks memory into RAM.
    "The VirtualLock function locks the specified region of the process's virtual address space into physical memory, ensuring that subsequent access to the region will not incur a page fault.
    All pages in the specified region must be committed. Memory protected with PAGE_NOACCESS cannot be locked.
    Locking pages into memory may degrade the performance of the system by reducing the available RAM and forcing the system to swap out other critical pages to the paging file. Each version of Windows has a limit on the maximum number of pages a process can lock. This limit is intentionally small to avoid severe performance degradation. Applications that need to lock larger numbers of pages must first call the SetProcessWorkingSetSize function to increase their minimum and maximum working set sizes. The maximum number of pages that a process can lock is equal to the number of pages in its minimum working set minus a small overhead.
    Pages that a process has locked remain in physical memory until the process unlocks them or terminates.
    To unlock a region of locked pages, use the VirtualUnlock function. Locked pages are automatically unlocked when the process terminates."
    The SetProcessWorkingSetSize functions allows you to get more locked memory.
    "The SetProcessWorkingSetSize function sets the minimum and maximum working set sizes for the specified process.
    The working set of a process is the set of memory pages currently visible to the process in physical RAM memory. These pages are resident and available for an application to use without triggering a page fault. The size of the working set of a process is specified in bytes. The minimum and maximum working set sizes affect the virtual memory paging behavior of a process.
    The working set of the specified process can be emptied by specifying the value -1 for both the minimum and maximum working set sizes.
    If the values of either dwMinimumWorkingSetSize or dwMaximumWorkingSetSize are greater than the process' current working set sizes, the specified process must have the SE_INC_BASE_PRIORITY_NAME privilege. Users in the Administrators and Power Users groups generally have this privilege. For more information about security privileges, see Privileges.
    The operating system allocates working set sizes on a first-come, first-served basis. For example, if an application successfully sets 40 megabytes as its minimum working set size on a 64-megabyte system, and a second application requests a 40-megabyte working set size, the operating system denies the second application's request.
    Using the SetProcessWorkingSetSize function to set an application's minimum and maximum working set sizes does not guarantee that the requested memory will be reserved, or that it will remain resident at all times. When the application is idle, or a low-memory situation causes a demand for memory, the operating system can reduce the application's working set. An application can use the VirtualLock function to lock ranges of the application's virtual address space in memory; however, that can potentially degrade the performance of the system.
    When you increase the working set size of an application, you are taking away physical memory from the rest of the system. This can degrade the performance of other applications and the system as a whole. It can also lead to failures of operations that require physical memory to be present; for example, creating processes, threads, and kernel pool. Thus, you must use the SetProcessWorkingSetSize function carefully. You must always consider the performance of the whole system when you are designing an application."
    But these functions will not be supported under Win98. I know from some other function which was stated to be not supported under Win98 were supported under Win98SE.
    But thats the time to get an answer from NI personal with more insight into what NIDAQ and the lvdaq.dll does.
    Waldemar
    Waldemar
    Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
    Don't forget to give Kudos to good answers and/or questions

  • Can any java process exceed the maximum memory allocated

    Hi,
    I have a basic question on the memory settings. Assume I have a java process where the memory settings are like:
    -Xmx1024m
    where the server capacity is say 8GB Then can the process exceed the allocated memory of 1GB and go further say upto 4 GB.
    If above thing is possible, how can we limit the process not to exceed the given limit? What settings need to be used.

    Krish8 wrote:
    Hi,
    I have a basic question on the memory settings. Assume I have a java process where the memory settings are like:
    -Xmx1024m
    where the server capacity is say 8GB Then can the process exceed the allocated memory of 1GB and go further say upto 4 GB.
    If above thing is possible, how can we limit the process not to exceed the given limit? What settings need to be used.Yes the used memory can exceed that if you e.g. are using memory mapped files. Don't know if you can restrict it unless your OS has some kind of support for it.
    Kaj

  • What is the default memory allocation for JVM

    Hi,
    Can anybody please let me know the default heap memory allocation(both min & max) for JVM, if we don't provide memory arguments (-Xms -Xmx) on 32-bit linux & windows machines having 4GB RAM?
    Thanks,
    Suresh

    user641407 wrote:
    Hi,
    Can anybody please let me know the default heap memory allocation(both min & max) for JVM, if we don't provide memory arguments (-Xms -Xmx) on 32-bit linux & windows machines having 4GB RAM?
    Starting with 5.0, per the Sun VM docs.
    http://download.oracle.com/javase/6/docs/technotes/tools/windows/java.html
    +"-Xmsn ... The default value is chosen at runtime based on system configuration."+
    +"-Xmxn ... The default value is chosen at runtime based on system configuration."+
    What other documentation are you looking for?

  • Queue of arrays without dynamic memory allocation

    Hey folks,
    I'm working on optimizing a timing critical VI. This VI is the
    producer in a producer consumer architecture. I'm trying to populate
    a queue from file in a manner that is as efficient as possible. My
    current plan of attack is:
    - read block of data from file and populate array (pre-allocated).
    - add array (always of the same size) to Queue with a max size defined
    (e.g. 50 elements)
    - This is in a while loop as is the standard producer consumer model.
    To improve the performance I would like to ensure that there is no
    dynamic memory allocation on the Queue's behalf. This is easily done,
    from what I understand, if the data type in the queue is of the same
    type (e.g. double, int). However, since the size of an array can vary
    does this mean that any queue of arrays will always dynamically
    allocate memory? Is there a way to ensure that the queue will always
    use the same memory as in a circular queue?
    Thanks,
    Steve

    Duplicate.
    Try to take over the world!

  • Free Stmt Handle NOT release Memory allocated inDefineByPos[LongRaw]

    My Question is : Why Free Stmt Handle does not release the memory OCI allocated during OCIDefineByPos for data type "Long Raw"
    Please notice the Bold Fonts in the dtrace logging. Ptr is the pointer returned by malloc. Size is the memory size allocated.
    I use OCI to fetch records, each round I will fetch 1000 records. I found memory increase round by round. So I use dtrace to probe the memory malloc/free. At the end of each round, I will free the handle of SQL Statement. According the documentation, all the sub handles belongs to stmt handle should be free also. But I noticed that memory allocated during DefinebyPos for LongRaw did not get released.
    1. The SQL Send to DB each round is the same.
    2. I do the "Define" each round. So It's actually a "RE-Define" each round.
    The length of Long Raw is 512K. Here's the dtrace result when I call the OCIDefineByPos. There's a 2MB memory allocated, I don't know the reason.
    CPU ID FUNCTION:NAME
    3 45971 free:entry Ptr=0x247652d0 Size=0 TS=1568035638893113 FreeTime=2008 Jul 20 23:26:09
    libc.so.1`free
    libclntsh.so.10.1`sktsfFree+0x18
    libclntsh.so.10.1`kpummfpg+0xb6
    libclntsh.so.10.1`kghfrempty+0x17c
    libclntsh.so.10.1`kghgex+0x13c
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kghgex+0x1e6
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kghgex+0x1e6
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kpuhhalo+0x1fd
    libclntsh.so.10.1`kpuex_reallocTempBufOnly+0x5f
    libclntsh.so.10.1`kpuertb_reallocTempBuf+0x36
    libclntsh.so.10.1`kpudefn+0x2d1
    libclntsh.so.10.1`kpudfn+0x39e
    libclntsh.so.10.1`OCIDefineByPos+0x38
    scrubber`_ZN29clsDatabasePhysicalHostOracle6DefineEN7voyager15eBayTypeDefEnumEiPhiPs11EnumCharSet+0x17f
    3 45966 malloc:return Ptr=0x252ad100 Size=524356 TS=1568035638916654 AllocTime=2008 Jul 20 23:26:09
    libc.so.1`malloc+0x49
    libclntsh.so.10.1`kpummapg+0xcc
    libclntsh.so.10.1`kghgex+0x1aa
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kghgex+0x1e6
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kghgex+0x1e6
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kpuhhalo+0x1fd
    libclntsh.so.10.1`kpuex_reallocTempBufOnly+0x5f
    libclntsh.so.10.1`kpuertb_reallocTempBuf+0x36
    libclntsh.so.10.1`kpudefn+0x2d1
    libclntsh.so.10.1`kpudfn+0x39e
    libclntsh.so.10.1`OCIDefineByPos+0x38
    scrubber`_ZN29clsDatabasePhysicalHostOracle6DefineEN7voyager15eBayTypeDefEnumEiPhiPs11EnumCharSet+0x17f
    scrubber`_ZN18clsDatabaseManager6DefineEN7voyager15eBayTypeDefEnumEiPhiPs+0x13c
    scrubber`_ZN17clsDatabaseOracle13DefineLongRawEiPhiPs+0x2f
    3 45971 free:entry Ptr=0x2476ab30 Size=0 TS=1568035639035363 FreeTime=2008 Jul 20 23:26:09
    libc.so.1`free
    libclntsh.so.10.1`sktsfFree+0x18
    libclntsh.so.10.1`kpummfpg+0xb6
    libclntsh.so.10.1`kghfrempty+0x17c
    libclntsh.so.10.1`kghgex+0x13c
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kghgex+0x1e6
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kghgex+0x1e6
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kpuhhalo+0x1fd
    libclntsh.so.10.1`kpuertb_reallocTempBuf+0x8f
    libclntsh.so.10.1`kpudefn+0x2d1
    libclntsh.so.10.1`kpudfn+0x39e
    libclntsh.so.10.1`OCIDefineByPos+0x38
    scrubber`_ZN29clsDatabasePhysicalHostOracle6DefineEN7voyager15eBayTypeDefEnumEiPhiPs11EnumCharSet+0x17f
    scrubber`_ZN18clsDatabaseManager6DefineEN7voyager15eBayTypeDefEnumEiPhiPs+0x13c
    3 45966 malloc:return Ptr=0x2532d150 Size=2097220 TS=1568035639040090 AllocTime=2008 Jul 20 23:26:09
    libc.so.1`malloc+0x49
    libclntsh.so.10.1`kpummapg+0xcc
    libclntsh.so.10.1`kghgex+0x1aa
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kghgex+0x1e6
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kghgex+0x1e6
    libclntsh.so.10.1`kghfnd+0x28a
    libclntsh.so.10.1`kghalo+0x669
    libclntsh.so.10.1`kpuhhalo+0x1fd
    libclntsh.so.10.1`kpuertb_reallocTempBuf+0x8f
    libclntsh.so.10.1`kpudefn+0x2d1
    libclntsh.so.10.1`kpudfn+0x39e
    libclntsh.so.10.1`OCIDefineByPos+0x38
    scrubber`_ZN29clsDatabasePhysicalHostOracle6DefineEN7voyager15eBayTypeDefEnumEiPhiPs11EnumCharSet+0x17f
    scrubber`_ZN18clsDatabaseManager6DefineEN7voyager15eBayTypeDefEnumEiPhiPs+0x13c
    scrubber`_ZN17clsDatabaseOracle13DefineLongRawEiPhiPs+0x2f
    scrubber`_ZN5dblib11DbExtractor18DefineLongRawFieldEiPhiPs+0x2b

    Assumption : You are using OCIHandleFree((dvoid*)DBctx->stmthp,(ub4)OCI_HTYPE_STMT);
    There are two scenarios here the LONG Raw mapping and release of memory.
    Unlike the other data types LONG Raw memory mapping is different since the data type requires more memory chunks.
    45971 free:entry Ptr=0x2476ab30 Size=0 TS=1568035639035363 FreeTime=2008 Jul 20 23:26:09
    libc.so.1`free
    Since from the above statement it clear that free is called . Hence there may be chance in other area of the code I suspect the memory leak is (Like native storage).
    Moreover the standard OS behavior is that it will not release the Heap/Stack until the process is complete even the free() is called by the process. This is for performance on memory management.Having said that it should not increase the memory drastically when not required.

  • Allocated heap memory goes up even when there is enough free memory

    Hi,
    Our Java application's memory usage keep growing. Further analysis of the heap memory using JProbe shows that the allocated heap memory goes up even when there is enough free memory available in the heap.
    When the process started, allocated heap memory was around 50MB and the memory used was around 8MB. After few hours, the inuse memory remains at 8MB (slight increase in KBs), but the allocated memory went upto 70MB.
    We are using JVM 1.5_10. What could be the reason for heap allocation going up even when there is enough free memory available in heap?
    -Rajesh.

    Hi Eric,
    Please check if there is any error or warning in the Event Viewer based on the data time?
    If there is any error, please post the event ID to help us to troubleshoot.
    Best Regards,
    Anna

  • When I view my phone capacity, there is an amount of memory allocated to "other"...what is this?

    When I view my phone capacity, there is an amount of memory allocated to "other"...what is this?

    depends on what data occupies your Other category on your iPhone and whether you could/want to delete it or not.
    Check your Camera Roll for lots of photos or shot videos, you can get rid of some which you consider wortty deleting. Regarding data allocated to each of your apps - this can vary and you can check that as described by John above. You can uninstall the apps on your iPhone you consider worth removing - this will remove their app data too.

  • Hyper-V, Dynamic Memory, Memory Demand more than Maximum memory

    Hi,
    I have found that for some VMs Demand Memory more that Maximum Memory set.
    Where can I found any documentation about this?

    A VM can 'demand' more memory than is possible'
    But it will never actually be given more then the maximum.
    In the VM the application is asking for more RAM from the virtual memory manager of the OS in the VM (not to be confused with any memory management that the hypervisor is doing).
    When the VM hits its Maximum setting it is no different than a physical machine hitting its physical RAM cap - the OS begins paging to give the application the additional RAM it is asking for.
    It simply means that you have a greedy application.  SQL and the Exchange mailbox role have a long history of being very greedy applications (SQL made many changes to work in concert with dynamic memory) - taking all of the RAM they could get.
    In your case, you have a startup of 32GB a minimum of 24GB and a Maximum of 36GB.  And the application in the VM would 'like' to have 54GB.  If you look in your VM OS you will probably find that it is paging to disk.
    What is your allocation setting?  The default of 20%  Higher?
    Personally - I see little value in using dynamic memory with such a small window of difference between the startup, minimum, and maximum.  It is as if you are trying to micro manage the feature, instead of allowing the feature to work as designed.
    Dynamic memory is designed to balance RAM between all of the VMs on a particular hypervisor at the same time.  And to allow use of all the RAM the machine has, if there is a workload that can use it.  If the VM wants 64GB, why not give it that. 
    Dynamic memory will not starve other VMs to give this VM more RAM (unless you give this VM a higher priority).  But it will take RAM away from a VM (if absolutely necessary) to allow another VM to meet its requirements.
    Any VM is always guaranteed its startup, at boot time.  And dynamic memory will not starve it below it minimum - and if the VM is not using RAM it will take RAM away down to the minimum.  And a VM will never be given more than the maximum, even
    if the VM wants more.
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • Short term memory allocator and Cache memor is out of memory

    Hi,
    I have three NW 6.5 sp8 servers in production. One of these, the one which holds Pervasive sql 9.7 began to show the following errors:
    Cache memory allocator out of available memory.
    Short term memory allocator is out of memory.
    360396 attempts to get more memory failed.
    request size in bytes 1048576 from Module SERVER.NLM
    I show here segstats.txt:
    *** Memory Pool Configuration for : DBASE_SERVER
    Time and date : 02:42:36 AM 12/02/2012
    Server version : NetWare 6.5 Support Pack 8
    Server uptime : 11d 04h 35m 28s
    SEG.NLM uptime : 0d 00h 01m 17s
    SEG.NLM version : v2.00.17
    Original Memory : 4,292,812,800 bytes (4.00 GB)
    ESM Memory : 805,302,272 bytes (768.0 MB)
    0xFFFFFFFF --------------------------------------------------------------
    | Kernel Reserved Space |
    | |
    | Size : 180,355,071 bytes (172.0 MB) |
    | |
    0xF5400000 --------------------------------------------------------------
    | User Address Space (L!=P) |
    | |
    | User Pool Size : 671,088,640 bytes (640.0 MB) |
    | High Water Mark : 559,710,208 bytes (533.8 MB) |
    | PM Pages In Use : 1,855,488 bytes (1.8 MB) |
    | |
    0xCD400000 --------------------------------------------------------------
    | Virtual Memory Address Space (L!=P) |
    | |
    | VM Address Space : 2,369,781,760 bytes (2.21 GB) |
    | Available : 801,435,648 bytes (764.3 MB) |
    | Total VM Pages : 800,870,400 bytes (763.8 MB) |
    | Free Clean VM : 785,563,648 bytes (749.2 MB) |
    | Free Cache VM : 15,306,752 bytes (14.6 MB) |
    | Total LP Pages : 0 bytes (0 KB) |
    | Free Clean LP : 0 bytes (0 KB) |
    | Free Cache LP : 0 bytes (0 KB) |
    | Free Dirty : 0 bytes (0 KB) |
    | NLM Memory In Use : 1,767,256,064 bytes (1.65 GB) |
    | NLM/VM Memory : 1,751,785,472 bytes (1.63 GB) |
    | Largest Segment : 2,097,152 bytes (2.0 MB) |
    | Lowest Kernel Page: 0 bytes (0 KB) |
    | : [0x00000000] |
    | High Water Mark : 2,243,096,576 bytes (2.09 GB) |
    | Alloc Failures : 370,804 |
    | |
    0x40000000 --------------------------------------------------------------
    | File System Address Space (L==P or L!=P) |
    | |
    | FS Address Space : 1,067,290,624 bytes (1017.8 MB) |
    | Available : 108,978,176 bytes (103.9 MB) |
    | Largest Segment : 3,362,816 bytes (3.2 MB) |
    | |
    | NSS Memory (85%) : 613,683,200 bytes (585.3 MB) |
    | NSS (avail cache) : 610,455,552 bytes (582.2 MB) |
    | |
    0x00627000 --------------------------------------------------------------
    | DOS / SERVER.NLM |
    | |
    | Size : 6,451,200 bytes (6.2 MB) |
    | |
    0x00000000 --------------------------------------------------------------
    Total NLMs loaded on the server: 307
    Top 20 Memory Consuming NLMs
    NLM Name Version Date Total NLM Memory
    ================================================== =============
    1. NWMKDE.NLM 9.70.07 Nov 14, 2008 813,035,623 bytes (775.4 MB)
    2. SERVER.NLM 5.70.08 Oct 3, 2008 467,216,096 bytes (445.6 MB)
    3. NSS.NLM 3.27.02 Nov 11, 2009 203,168,848 bytes (193.8 MB)
    4. NCPL.NLM 3.02 May 6, 2009 41,854,837 bytes (39.9 MB)
    5. NWSQLMGR.NLM 9.70.07 Nov 14, 2008 39,309,132 bytes (37.5 MB)
    6. DS.NLM 20217.07 Jan 30, 2009 24,851,303 bytes (23.7 MB)
    7. APACHE2.NLM 2.00.63 Apr 25, 2008 19,863,493 bytes (18.9 MB)
    8. CIOS.NLM 1.60 Feb 12, 2008 10,569,567 bytes (10.1 MB)
    9. OWCIMOMD.NLM 3.02 Nov 27, 2007 9,318,616 bytes (8.9 MB)
    10. APRLIB.NLM 0.09.17 Apr 25, 2008 8,959,760 bytes (8.5 MB)
    11. APACHE2.NLM 2.00.63 Apr 25, 2008 7,702,469 bytes (7.3 MB)
    12. FATFS.NLM 1.24 Aug 27, 2007 5,859,413 bytes (5.6 MB)
    13. NWPA.NLM 3.21.02 Oct 29, 2008 4,990,686 bytes (4.8 MB)
    14. PKI.NLM 3.32 Aug 25, 2008 4,069,957 bytes (3.9 MB)
    15. WS2_32.NLM 6.24.01 Feb 14, 2008 3,623,596 bytes (3.5 MB)
    16. NWMPM100.NLM 9.70.07 Nov 14, 2008 3,597,747 bytes (3.4 MB)
    17. NWODBCEI.NLM 9.70.07 Nov 14, 2008 3,459,159 bytes (3.3 MB)
    18. PORTAL.NLM 4.03 Sep 22, 2008 3,404,576 bytes (3.2 MB)
    19. JVM.NLM 1.43 Oct 16, 2008 2,701,919 bytes (2.6 MB)
    20. NLDAP.NLM 20218.11 Jan 30, 2009 2,579,131 bytes (2.5 MB)
    Top 20 NLM - Memory Trends
    NLM Name Original Memory Current Change
    ================================================== =========
    1. NWMKDE.NLM 842,068,071 bytes 813,035,623 bytes -27.7 MB
    2. SERVER.NLM 463,894,240 bytes 467,216,096 bytes 3.2 MB
    3. NSS.NLM 203,168,848 bytes 203,168,848 bytes 0 KB
    4. NCPL.NLM 41,850,741 bytes 41,854,837 bytes 4 KB
    5. NWSQLMGR.NLM 39,092,044 bytes 39,309,132 bytes 212 KB
    6. DS.NLM 24,896,359 bytes 24,851,303 bytes -44 KB
    7. APACHE2.NLM 19,855,301 bytes 19,863,493 bytes 8 KB
    8. CIOS.NLM 10,569,567 bytes 10,569,567 bytes 0 KB
    9. OWCIMOMD.NLM 9,277,656 bytes 9,318,616 bytes 40 KB
    10. APRLIB.NLM 8,959,760 bytes 8,959,760 bytes 0 KB
    11. APACHE2.NLM 7,702,469 bytes 7,702,469 bytes 0 KB
    12. FATFS.NLM 5,859,413 bytes 5,859,413 bytes 0 KB
    13. NWPA.NLM 4,957,918 bytes 4,990,686 bytes 32 KB
    14. PKI.NLM 4,135,493 bytes 4,069,957 bytes -64 KB
    15. WS2_32.NLM 3,619,500 bytes 3,623,596 bytes 4 KB
    16. NWMPM100.NLM 3,597,747 bytes 3,597,747 bytes 0 KB
    17. NWODBCEI.NLM 3,459,159 bytes 3,459,159 bytes 0 KB
    18. PORTAL.NLM 3,400,480 bytes 3,404,576 bytes 4 KB
    19. JVM.NLM 2,701,919 bytes 2,701,919 bytes 0 KB
    20. NLDAP.NLM 2,505,403 bytes 2,579,131 bytes 72 KB
    Logical Memory Summary Information
    ================================================== ===============================
    File System Cache Information
    FS Cache Free : 4,591,616 bytes (4.4 MB)
    FS Cache Fragmented : 104,386,560 bytes (99.6 MB)
    FS Cache Largest Segment : 3,362,816 bytes (3.2 MB)
    Logical System Cache Information
    LS Cache Free : 0 bytes (0 KB)
    LS Cache Fragmented : 722,448,384 bytes (689.0 MB)
    LS OS Reserved Data : 333,455,360 bytes (318.0 MB)
    LS Cache Largest Segment : 2,097,152 bytes (2.0 MB)
    LS Cache Largest Position : 2DE00000
    Summary Statistics
    Total Address Space : 4,294,967,296 bytes (4.00 GB)
    Total Free : 4,591,616 bytes (4.4 MB)
    Total Fragmented : 826,834,944 bytes (788.5 MB)
    Highest Physical Address : CFE53000
    User Space : 671,088,640 bytes (640.0 MB)
    User Space (High Water Mark) : 559,710,208 bytes (533.8 MB)
    NLM Memory (High Water Mark) : 2,243,096,576 bytes (2.09 GB)
    Kernel Address Space In Use : 2,572,759,040 bytes (2.40 GB)
    Available Kernel Address Space : 43,929,600 bytes (41.9 MB)
    Memory Summary Screen (.ms)
    ================================================== ===============================
    KNOWN MEMORY Bytes Pages Bytes Pages
    Server: 3487425552 851422 Video: 8192 2
    Dos: 86000 20 Other: 131072 32
    FS CACHE KERNEL NLM MEMORY
    Original: 3483172864 850384 Code: 46854144 11439
    Current: 108978176 26606 Data: 27242496 6651
    Dirty: 0 0 Sh Code: 49152 12
    Largest seg: 3362816 821 Sh Data: 20480 5
    Non-Movable: 81920 20 Help: 172032 42
    Other: 4235538432 4292855635 Message: 1236992 302
    Avail NSS: 610439168 149033 Alloc L!=P: 1661366272 405607
    Movable: 8192 2 Alloc L==P: 14843904 3624
    Total: 1751785472 427682
    VM SYSTEM
    Free clean VM: 785563648 191788
    Free clean LP: 0 0
    Free cache VM: 15306752 3737
    Free cache LP: 0 0
    Free dirty: 0 0
    In use: 1855488 453
    Total: 801435648 195663
    Memory Configuration (set parameters)
    ================================================== ==============================
    Auto Tune Server Memory = ON
    File Cache Maximum Size = 1073741825
    File Service Memory Optimization = 1
    Logical Space Compression = 1
    Garbage Collection Interval (ON) = 299.9 seconds
    VM Garbage Collector Period (ON) = 300.0 seconds
    server -u<number> = 671088640
    NSS Configuration File:
    C:\NWSERVER\NSSSTART.CFG
    File does not exist,
    or is zero byte in size.
    DS Configuration File:
    SYS:\_NETWARE\_NDSDB.INI
    File does not exist,
    or is zero byte in size.
    TSAFS Memory Information/Configuration
    ================================================== ==============================
    Cache Memory Threshold : 1%
    Read Buffer Size : 65536 bytes
    Max Data Sets for Read Ahead : 2
    Read Threads Per Job : 4
    NSS Memory Information/Configuration
    ================================================== ==============================
    Current NSS Memory Settings
    Cache Balance Percentage : 85%
    Cache Memory Allocated : 585.3 MB
    Available Cache from NSS : 582.2 MB
    Current NSS Caching Percentages
    Buffer cache hit percentage : 63%
    Name Tree cache hit percentage : 94%
    File cache hit percentage : 99%
    NSS Flush Status: Not Flushed
    Server High/Low Water Mark Values
    ================================================== ==============================
    NLM Memory High Water Mark = 2,243,096,576 bytes
    File System High Water Mark = 443,108 bytes
    User Space Information:
    User Space High Water Mark = 559,710,208 bytes
    Committed Pages High Water Mark = 87 pages
    Mapped VM Pages High Water Mark = 3,875 pages
    Reserved Pages High Water Mark = 400,103 pages
    Swapped Pages High Water Mark = 3,785 pages
    Available Low Water Mark = 294,670,336
    ESM Memory High Water Mark = 173 pages
    It seems that server.nlm is growing without limits. When tat occurs, I have the mentioned errors.
    Though NWMKDE seems to have grown. It remains steady around the showed values.
    I'm not brave enough to apply the memcalc's recommended fixes because the following line:
    set file cache maximum size=822083584
    returns an error saying the minimun value should be 1073741824.
    Can someone help me because I'm completely blind here.
    Thanks in advance.
    Gabriel

    I take it this is primarily a database server, in which case it's OK that Btrieve is using so much memory? You wouldn't want this to be a general file server too. Is the memory error causing any actual problem?
    Server is asking for only 1mb, and due to fragmentation there is little free memory (actually 2mb left, which is a little odd, but neither here nor there).
    Also, let's see your bti.cfg, which is the Btrieve config file. I'll paste in below an ArcServe TID on Btrieve using excessive memory:
    Symptoms
    Btrieve was upgraded to version 8.5 during the installation of ARCserve r11.1. The cachesize in the BTI.cfg microkernel section is at 20 MB (20480). (Pervasive would like this setting placed to 20% of the server memory or database size which ever is less.) The server will keep adding 20 additional Megs of memory to the total amount of memory the server is using for database transactions after each backup job. This can be verified by performing the following at the server console:
    LOAD MONITOR
    Scroll down to System Resources under Available Options and hit enter.
    Scroll down to Alloc Memory (Bytes) and hit enter.
    Locate NWMKDE.nlm in the Resource Tags list.
    Sort by memory bytes and you will slowly see nwmkde.nlm move to the top of the usage list. Unless the server is rebooted the small memory allocations stays at the increased amount.
    Explanation
    Starting with Btrieve version 8.5 and higher, Pervasive has been working to make the Btrieve database more dynamic. They have created a two-tier memory allocation approach. The first level is controlled by the cache size setting in the BTI.cfg. If this becomes inadequate, the second level will be accessed. The default setting for the second level is 60% of the server's total memory.
    The following line in the BTI.cfg will control the second level of memory caching:
    MaxCacheUsage=60; default is 60% of memory.
    An example would be a server with 100 MB of memory and the following settings in sys:\system\bti.cfg:
    [microkernel]
    cachesize=20480
    MaxCacheUsage=60
    This will cause the nwmkde.nlm to use 20 MB (20480) of memory initially and grow up to 60 percent of the total server memory or 60 MB.
    Now you also have to throw Max worker threads into the mix. A setting of Max worker threads = 3 in the BTI.cfg > Btrieve Communications Manager section will also use server memory. It will use 1 MB per thread. In this example, 3 Megs of additional memory will be used. That will bring the total amount of memory used by nwmkde.nlm to 20 MB (20480) + 3 MB = 23 MB when the server is first booted. After running some backups, this number could go up to as high as 60 MB (60% of server memory) if the server dynamically requires it.
    Resolution
    The MaxCacheUsage=60 setting must be set down from this 60% number. Pervasive recommends setting this from 0 to 20. The server needs to be rebooted for this change to take effect.

  • ICMP Timeout Alarm due to TCP Protocol Memory Allocation Failure ?

    Hello Experts ,
      >> Device uptime suggests there was no reboot
    ABCSwitch uptime is 28 weeks, 13 hours, 50 minutes
    System returned to ROM by power-on
    System restarted at 13:09:45 UTC Mon Aug 5 2013
    System image file is "flash:c2950-i6k2l2q4-mz.121-22.EA12.bin"
    >> But observed logs mentioning Memory Allocation Failure for TCP Protocol Process ( Process ID 43) due to Memory Fragmentation
    003943: Feb 18 02:14:27.393 UTC: %SYS-2-MALLOCFAIL: Memory allocation of 36000 bytes failed from 0x801E876C, alignment 0
    Pool: Processor Free: 120384 Cause: Memory fragmentation
    Alternate Pool: I/O Free: 682800 Cause: Memory fragmentation
    -Process= "TCP Protocols", ipl= 0, pid= 43
    -Traceback= 801C422C 801C9ED0 801C5264 801E8774 801E4CDC 801D9A8C 8022E324 8022E4BC
    003944: Feb 18 02:14:27.397 UTC: %SYS-2-CFORKMEM: Process creation of TCP Command failed (no memory).
    -Process= "TCP Protocols", ipl= 0, pid= 43
    -Traceback= 801E4D54 801D9A8C 8022E324 8022E4BC
    According to Cisco documentation for Troubleshooting Memory issues on Cisco IOS 12.1 (http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/6507-mallocfail.html#tshoot4 ), which suggests the TCP Protocols Process could not be started due to Memory being fragmented
    Memory Fragmentation Problem or Bug
    This situation means that a process has consumed a large amount of processor memory and then released most or all of it, leaving fragments of memory still allocated either by this process, or by other processes that allocated memory during the problem. If the same event occurs several times, the memory may fragment into very small blocks, to the point where all processes requiring a larger block of memory cannot get the amount of memory that they need. This may affect router operation to the extent that you cannot connect to the router and get a prompt if the memory is badly fragmented.
    This problem is characterized by a low value in the "Largest" column (under 20,000 bytes) of the show memory command, but a sufficient value in the "Freed" column (1MB or more), or some other wide disparity between the two columns. This may happen when the router gets very low on memory, since there is no defragmentation routine in the IOS.
    If you suspect memory fragmentation, shut down some interfaces. This may free the fragmented blocks. If this works, the memory is behaving normally, and all you have to do is add more memory. If shutting down interfaces doesn't help, it may be a bug. The best course of action is to contact your Cisco support representative with the information you have collected.
    >>Further TCP -3- FORKFAIL logs were seen
    003945: Feb 18 02:14:27.401 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    003946: Feb 18 02:14:27.585 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    003947: Feb 18 02:14:27.761 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    003948: Feb 18 02:14:27.929 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    003949: Feb 18 02:14:29.149 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    According to Error Explanation from Cisco Documentation (http://www.cisco.com/c/en/us/td/docs/ios/12_2sx/system/messages/122sxsms/sm2sx09.html#wp1022051)
    suggests the TCP handles from a client could not be created or initialized
    Error Message %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    Explanation The system failed to create a process to handle requests  from a client. This condition could be caused by insufficient  memory.
    Recommended Action Reduce other system activity to ease  memory demands.
    But I am still not sure about the exact root cause is as
    1.The GET/GETNEXT / GET BULK messages from SNMP Manager (Here, IBM Tivoli Netcool  ) uses default SNMP Port 161 which is
       UDP and not TCP
    2. If its ICMP Polling failure from IBM Tivoli Netcool , ICMP is Protocol Number 1 in Internet Layer of TCP/IP Protocol Suite  and TCP is Protocol                 Number 6 in the Transport Layer of TCP/IP Protocol Suite .
    So I am still not sure how TCP Protocol Process Failure could have caused ICMP Timeout . Please help !
    Could you please help me on what TCP Protocol Process handles in a Cisco Switch ?
    Regards,
    Anup

    Hello Experts ,
      >> Device uptime suggests there was no reboot
    ABCSwitch uptime is 28 weeks, 13 hours, 50 minutes
    System returned to ROM by power-on
    System restarted at 13:09:45 UTC Mon Aug 5 2013
    System image file is "flash:c2950-i6k2l2q4-mz.121-22.EA12.bin"
    >> But observed logs mentioning Memory Allocation Failure for TCP Protocol Process ( Process ID 43) due to Memory Fragmentation
    003943: Feb 18 02:14:27.393 UTC: %SYS-2-MALLOCFAIL: Memory allocation of 36000 bytes failed from 0x801E876C, alignment 0
    Pool: Processor Free: 120384 Cause: Memory fragmentation
    Alternate Pool: I/O Free: 682800 Cause: Memory fragmentation
    -Process= "TCP Protocols", ipl= 0, pid= 43
    -Traceback= 801C422C 801C9ED0 801C5264 801E8774 801E4CDC 801D9A8C 8022E324 8022E4BC
    003944: Feb 18 02:14:27.397 UTC: %SYS-2-CFORKMEM: Process creation of TCP Command failed (no memory).
    -Process= "TCP Protocols", ipl= 0, pid= 43
    -Traceback= 801E4D54 801D9A8C 8022E324 8022E4BC
    According to Cisco documentation for Troubleshooting Memory issues on Cisco IOS 12.1 (http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/6507-mallocfail.html#tshoot4 ), which suggests the TCP Protocols Process could not be started due to Memory being fragmented
    Memory Fragmentation Problem or Bug
    This situation means that a process has consumed a large amount of processor memory and then released most or all of it, leaving fragments of memory still allocated either by this process, or by other processes that allocated memory during the problem. If the same event occurs several times, the memory may fragment into very small blocks, to the point where all processes requiring a larger block of memory cannot get the amount of memory that they need. This may affect router operation to the extent that you cannot connect to the router and get a prompt if the memory is badly fragmented.
    This problem is characterized by a low value in the "Largest" column (under 20,000 bytes) of the show memory command, but a sufficient value in the "Freed" column (1MB or more), or some other wide disparity between the two columns. This may happen when the router gets very low on memory, since there is no defragmentation routine in the IOS.
    If you suspect memory fragmentation, shut down some interfaces. This may free the fragmented blocks. If this works, the memory is behaving normally, and all you have to do is add more memory. If shutting down interfaces doesn't help, it may be a bug. The best course of action is to contact your Cisco support representative with the information you have collected.
    >>Further TCP -3- FORKFAIL logs were seen
    003945: Feb 18 02:14:27.401 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    003946: Feb 18 02:14:27.585 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    003947: Feb 18 02:14:27.761 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    003948: Feb 18 02:14:27.929 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    003949: Feb 18 02:14:29.149 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    -Traceback= 8022E33C 8022E4BC
    According to Error Explanation from Cisco Documentation (http://www.cisco.com/c/en/us/td/docs/ios/12_2sx/system/messages/122sxsms/sm2sx09.html#wp1022051)
    suggests the TCP handles from a client could not be created or initialized
    Error Message %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
    Explanation The system failed to create a process to handle requests  from a client. This condition could be caused by insufficient  memory.
    Recommended Action Reduce other system activity to ease  memory demands.
    But I am still not sure about the exact root cause is as
    1.The GET/GETNEXT / GET BULK messages from SNMP Manager (Here, IBM Tivoli Netcool  ) uses default SNMP Port 161 which is
       UDP and not TCP
    2. If its ICMP Polling failure from IBM Tivoli Netcool , ICMP is Protocol Number 1 in Internet Layer of TCP/IP Protocol Suite  and TCP is Protocol                 Number 6 in the Transport Layer of TCP/IP Protocol Suite .
    So I am still not sure how TCP Protocol Process Failure could have caused ICMP Timeout . Please help !
    Could you please help me on what TCP Protocol Process handles in a Cisco Switch ?
    Regards,
    Anup

  • Message "Could not save because there is not enough memory (RAM)"

    Running Mac OS9.2.2 Suddenly start to get and error message " An error occured saving the enclosure "file name" Not enough memory" when trying to save an attachment in Microsoft Outlook. Same thing with Adobe Photoshop - when trying to save an any new file - message "Could not save because there is not enough memory (RAM)".
    Already Tried:
    During several freezes, suddenly my mac stop recognize any extensions. When used Microsoft Outlook and tried download an attachment got an error message type 3. So I create a new set in extensions manager and get ride of Type 3 error, but get a new error message "Not enough memory" when try to save an attachment, or "Not enough RAM" - when try to save an EPS file in Adobe Photoshop.
    In Outlook ("Get Info" section)changed memory size:
    Suggested Size: 7168 K
    Minimum Size: 16000 K
    Preferred Size: 16000 K
    In all mailboxes - there are not that many messages and they are not heavy at all, I checked them all before. And I rebuilt/compressed Outlook database - holding Option while restarted Outlook...
    Adobe Photoshop - started acting weird at same time. Even if I want to open a file through the menu: File - Open - it gives me the same message.
    Who has any clue - please help!!!

    Hi, Mike -
    I have Outlook Express's Preferred memory allocation set to 45000K, and don't have any problems with attachments. Don't be afraid of increasing OE's Preferred memory allocation (nor IE's, either - I have that set to 65000K).
    How large is the Messages file used by the account you're using in Outlook? You can examine that file here - (hard drive) >> Documents >> Microsoft User Data >> Identities >> (account folder, either the default "Main Identity" or one you've created) >> Messages.
    It seems that the Messages file grows with each email received; but does not shrink when an email is deleted. Over time, especially when lots of attachments are involved, that file can get huge.
    One way to help it not get too big is to -
    • delete attachments after copying them to the desktop. In case you're not familiar with the easy way to copy an attachment to the desktop - select the email so it opens; click the small triangle next to the legend "Attachments" between the upper pane and the lower pane in Outlook's main window; drag the attachment from the list out onto the desktop. It will be extracted and copied to that location. Once that has been done you can delete the attachment from the email with which it arrived.
    • after purging your emails of unneeded emails and attachments, compact the file. To do that, quit Outlook if it is running. Then hold down the Option key and start up Outlook. A splash screen will appear asking if you want to compact its database files - click yes. Follow the prompts.
    Compacting OE's database can also fix some instances of a damaged database that can't be used.
    If you could answer a few more questins, perhaps we can offer additional suggestions -
    1) How much RAM do you have installed? That means the physical RAM, not counting Virtual Memory in use, if any.
    2) How full is your hard drive - how big is it, how much free space is left unused?
    3) When was the last time you rebuilt the desktop file?

  • Memory allocation model on Windows

    We have an application server with 16 GB of RAM and 54 GB of SWAP.
    The application server run on a Windows 2003 IA64 SP2.
    We are using 6.40_ex2 kernel.
    When we run intensive memory program (program that use a lot of memory in internal table) we see that all the EM is allocated in PM.
    HM too is allocated in PM until the PM rech less than 200 MB.
    When the PM is less than 200 MB the total VM used on the server is less than 25 GB (EM: 10 GB; HM < 10 GB).
    There are SAP kernel rules that defined what allocate in RAM and what allocate in Paging file?
    We think that should be a better distribution from RAM and SWAP but we don't know if it is a right consideration.

    Essbase should use the amount of memory allocated in the Database settings, (plus some overhead for the Agent / App Server itself, which should be nowhere near 4G).Take a look at the database settings within the application. Look at the Index Cache, Data Cache and Data File Cache to ensure are not set absurdly high. As a test, leave them at their default values - worry about tuning them later.Also, how many Essbase applications are running on this server? Is it just the one?Regards,Jade-----------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

  • LabVIEW Memory Allocation

    Hey,
    Is it possible to allocate predefined RAM Memory and accumulate data's into it?
    Before going in to detail – I am currently looking to write the inspection results in database for statistical analysis. I hope it will always consume some time to write it in database for each component / iteration. So decided to accumulate all the data in memory and write it at one shot.
    In detail, user has to inputs the memory size via front panel control. Let us assume for writing 1 row of string information occupies “XX” bytes. (Not yet sure how to calculate memory size of 1D string array of 10 elements (max of 20 character in each string)). Dividing the user input memory size with 1 row of memory size will give how many rows we can write at maximum say “N”.
    Use the for loop with “N” iteration and accumulates the 1D info to 2D array of information (auto indexing) and write it in Database at one shot.
    Any help or direction may helps a lot. 
    Waiting for the reply 
    Sasi.
    Certified LabVIEW Associate Developer
    If you can DREAM it, You can DO it - Walt Disney

     As far I know LabVIEW internally handles the memory allocation and we don't have any option to allocate it. There might be a way by using a windows dll but no direct function atleast.
    As you said you are going to use the for loop, in this case LabVIEW pre-allocates the memory depending on the data type and you don't have to worry about that. For details about the memory according to the data type you can check this link.
    The best solution is the one you find it by yourself

  • SQL server 2012 : There is insufficient system memory in resource pool 'internal' to run this query

    We have recently upgraded from SQL server 2008 to SQL server 2012.
    We are getting this error when browsing to several pages on our website.
     There is insufficient system memory in resource pool 'internal' to run this query
    Most of the pages just try to do sql statements or stored procedures. I found a fix related to this error for sql 2012
    http://support.microsoft.com/kb/2769594/en-gb
    I did install it on server but the problem still remains.
    I have increased Maximum server memory to 20 GB to see if it will affect but it didnt.
    Memory on server is 32GB
    This is the sql version we have
    Microsoft SQL Server 2012 (SP1) - 11.0.3393.0 (X64)
        Oct 25 2013 19:04:40
        Copyright (c) Microsoft Corporation
        Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    How can i solve this error?It keeps on appearing when browsing .net website

    This is the ouptut of memory status
    Process/System Counts Value
    Available Physical Memory 6559842304
    Available Virtual Memory 8741595508736
    Available Paging File 17090838528
    Working Set 21094821888
    Percent of Committed Memory in WS 100
    Page Faults 160487165
    System physical memory high 1
    System physical memory low 0
    Process physical memory low 0
    Process virtual memory low 0
    Memory Manager KB
    VM Reserved 51506548
    VM Committed 20445040
    Locked Pages Allocated 0
    Large Pages Allocated 0
    Emergency Memory 1024
    Emergency Memory In Use 16
    Target Committed 20480008
    Current Committed 20445040
    Pages Allocated 6298528
    Pages Reserved 717408
    Pages Free 13820616
    Pages In Use 5143472
    Page Alloc Potential 14312512
    NUMA Growth Phase 0
    Last OOM Factor 1
    Last OS Error 0
    Memory node Id = 0 KB
    VM Reserved 51504948
    VM Committed 10218952
    Locked Pages Allocated 0
    Pages Allocated 1651360
    Pages Free 8323696
    Target Committed 10239992
    Current Committed 10218952
    Foreign Committed 96
    Away Committed 0
    Taken Away Committed 0
    Memory node Id = 1 KB
    VM Reserved 1536
    VM Committed 10226068
    Locked Pages Allocated 0
    Pages Allocated 4647208
    Pages Free 5496896
    Target Committed 10239992
    Current Committed 10226072
    Foreign Committed 0
    Away Committed 0
    Taken Away Committed 0
    Memory node Id = 64 KB
    VM Reserved 0
    VM Committed 20
    Locked Pages Allocated 0
    MEMORYCLERK_SQLGENERAL (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 19136
    MEMORYCLERK_SQLGENERAL (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 144
    MEMORYCLERK_SQLGENERAL (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 19280
    MEMORYCLERK_SQLBUFFERPOOL (node 0) KB
    VM Reserved 841608
    VM Committed 151560
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 1081360
    MEMORYCLERK_SQLBUFFERPOOL (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 1119416
    MEMORYCLERK_SQLBUFFERPOOL (Total) KB
    VM Reserved 841608
    VM Committed 151560
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 2200776
    MEMORYCLERK_SQLQUERYEXEC (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 5768
    MEMORYCLERK_SQLQUERYEXEC (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 9624
    MEMORYCLERK_SQLQUERYEXEC (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 15392
    MEMORYCLERK_SQLOPTIMIZER (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 2480
    MEMORYCLERK_SQLUTILITIES (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 112
    MEMORYCLERK_SQLUTILITIES (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    MEMORYCLERK_SQLUTILITIES (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 128
    MEMORYCLERK_SQLSTORENG (node 0) KB
    VM Reserved 4800
    VM Committed 4800
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 7928
    MEMORYCLERK_SQLSTORENG (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 5856
    MEMORYCLERK_SQLSTORENG (Total) KB
    VM Reserved 4800
    VM Committed 4800
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 13784
    MEMORYCLERK_SQLCONNECTIONPOOL (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 1184
    MEMORYCLERK_SQLCONNECTIONPOOL (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 536
    MEMORYCLERK_SQLCONNECTIONPOOL (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 1720
    MEMORYCLERK_SQLCLR (node 0) KB
    VM Reserved 9450752
    VM Committed 10664
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 60648
    MEMORYCLERK_SQLSERVICEBROKER (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 528
    MEMORYCLERK_SQLHTTP (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    MEMORYCLERK_SNI (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 40
    MEMORYCLERK_SNI (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 56
    MEMORYCLERK_SNI (node 64) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    MEMORYCLERK_SNI (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 112
    MEMORYCLERK_FULLTEXT (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 297936
    MEMORYCLERK_FULLTEXT (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 3406024
    MEMORYCLERK_FULLTEXT (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 3703960
    MEMORYCLERK_SQLXP (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    MEMORYCLERK_BHF (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 152
    MEMORYCLERK_BHF (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 184
    MEMORYCLERK_BHF (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 336
    MEMORYCLERK_SQLQERESERVATIONS (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 841952
    MEMORYCLERK_XE_BUFFER (node 0) KB
    VM Reserved 3072
    VM Committed 3072
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 0
    MEMORYCLERK_XE_BUFFER (node 1) KB
    VM Reserved 1536
    VM Committed 1536
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 0
    MEMORYCLERK_XE_BUFFER (Total) KB
    VM Reserved 4608
    VM Committed 4608
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 0
    MEMORYCLERK_XTP (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    MEMORYCLERK_HOST (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 40
    MEMORYCLERK_SOSNODE (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 34168
    MEMORYCLERK_SOSNODE (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 11664
    MEMORYCLERK_SOSNODE (node 64) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 2600
    MEMORYCLERK_SOSNODE (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 48432
    MEMORYCLERK_SOSOS (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 192
    MEMORYCLERK_SOSMEMMANAGER (node 0) KB
    VM Reserved 85560
    VM Committed 85416
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 0
    MEMORYCLERK_FULLTEXT_SHMEM (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 576
    SM Committed 576
    Pages Allocated 0
    MEMORYCLERK_SQLSERVICEBROKERTRANSPORT (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 200
    MEMORYCLERK_FILETABLE (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    MEMORYCLERK_XE (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 3440
    MEMORYCLERK_SQLLOGPOOL (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 4208
    MEMORYCLERK_LWC (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 192
    MEMORYCLERK_FSCHUNKER (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 48
    CACHESTORE_OBJCP (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 5848
    CACHESTORE_SQLCP (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 29664
    CACHESTORE_PHDR (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 4616
    CACHESTORE_XPROC (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 32
    CACHESTORE_TEMPTABLES (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    CACHESTORE_NOTIF (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    CACHESTORE_VIEWDEFINITIONS (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    CACHESTORE_XMLDBTYPE (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_XMLDBELEMENT (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_XMLDBATTRIBUTE (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_STACKFRAMES (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_STACKFRAMES (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_STACKFRAMES (node 64) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_STACKFRAMES (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 24
    CACHESTORE_BROKERTBLACS (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 48
    CACHESTORE_BROKERKEK (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_BROKERDSH (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_BROKERUSERCERTLOOKUP (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_BROKERRSB (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_BROKERREADONLY (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 32
    CACHESTORE_BROKERTO (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    CACHESTORE_EVENTS (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    CACHESTORE_SEHOBTCOLUMNATTRIBUTE (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 400
    CACHESTORE_SYSTEMROWSET (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 1056
    CACHESTORE_SYSTEMROWSET (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 480
    CACHESTORE_SYSTEMROWSET (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 1536
    CACHESTORE_CONVPRI (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 32
    CACHESTORE_CONVPRI (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    CACHESTORE_CONVPRI (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 48
    CACHESTORE_FULLTEXTSTOPLIST (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 56
    CACHESTORE_SEARCHPROPERTYLIST (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    CACHESTORE_COLUMNSTOREOBJECTPOOL (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 192
    CACHESTORE_XML_SELECTIVE_DG (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    USERSTORE_SCHEMAMGR (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8896
    USERSTORE_DBMETADATA (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 5088
    USERSTORE_DBMETADATA (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 4768
    USERSTORE_DBMETADATA (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 9856
    USERSTORE_TOKENPERM (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8104
    USERSTORE_TOKENPERM (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 448
    USERSTORE_TOKENPERM (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8552
    USERSTORE_OBJPERM (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 1640
    USERSTORE_OBJPERM (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 600
    USERSTORE_OBJPERM (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 2240
    USERSTORE_SXC (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 160
    USERSTORE_SXC (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 168
    USERSTORE_SXC (node 64) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 8
    USERSTORE_SXC (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 336
    OBJECTSTORE_LBSS (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 368
    OBJECTSTORE_LBSS (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 296
    OBJECTSTORE_LBSS (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 664
    OBJECTSTORE_SNI_PACKET (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 616
    OBJECTSTORE_SNI_PACKET (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 648
    OBJECTSTORE_SNI_PACKET (node 64) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 56
    OBJECTSTORE_SNI_PACKET (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 1320
    OBJECTSTORE_SERVICE_BROKER (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 496
    OBJECTSTORE_LOCK_MANAGER (node 0) KB
    VM Reserved 65540
    VM Committed 65540
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 11816
    OBJECTSTORE_LOCK_MANAGER (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 11632
    OBJECTSTORE_LOCK_MANAGER (node 64) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 24
    OBJECTSTORE_LOCK_MANAGER (Total) KB
    VM Reserved 65540
    VM Committed 65540
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 23472
    OBJECTSTORE_SECAUDIT_EVENT_BUFFER (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    OBJECTSTORE_XACT_CACHE (node 0) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 2224
    OBJECTSTORE_XACT_CACHE (node 1) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 2488
    OBJECTSTORE_XACT_CACHE (node 64) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 16
    OBJECTSTORE_XACT_CACHE (Total) KB
    VM Reserved 0
    VM Committed 0
    Locked Pages Allocated 0
    SM Reserved 0
    SM Committed 0
    Pages Allocated 4728
    Buffer Pool Value
    Database 274830
    Simulated 0
    Target 4096000
    Dirty 507
    In IO 0
    Latched 1
    Page Life Expectancy 11941
    Procedure Cache Value
    TotalProcs 333
    TotalPages 5914
    InUsePages 345
    Global Memory Objects Pages
    Resource 401
    Locks 2934
    XDES 561
    DirtyPageTracking 24
    SETLS 24
    SubpDesc Allocators 165
    SE SchemaManager 559
    SE Column Metadata Cache 549
    SE Column Metadata Cache Store 3
    SQLCache 270
    Replication 2
    ServerGlobal 52
    XP Global 2
    SortTables 3
    Query Memory Objects (internal) Value
    Grants 2
    Waiting 0
    Available 1677087
    Current Max 1814852
    Future Max 1814852
    Physical Max 1854482
    Next Request 0
    Waiting For 0
    Cost 0
    Timeout 0
    Wait Time 0
    Small Query Memory Objects (internal) Value
    Grants 0
    Waiting 0
    Available 95518
    Current Max 95518
    Future Max 95518
    Remote Query Memory Objects (internal) Value
    Grants 0
    Waiting 0
    Available 926250
    Current Max 926250
    Optimization Queue (internal) Value
    Overall Memory 17039360000
    Target Memory 16709148672
    Last Notification 1
    Timeout 6
    Early Termination Factor 5
    Small Gateway (internal) Value
    Configured Units 96
    Available Units 95
    Acquires 1
    Waiters 0
    Threshold Factor 380000
    Threshold 380000
    Medium Gateway (internal) Value
    Configured Units 24
    Available Units 24
    Acquires 0
    Waiters 0
    Threshold Factor 12
    Threshold 1392429056
    Big Gateway (internal) Value
    Configured Units 1
    Available Units 1
    Acquires 0
    Waiters 0
    Threshold Factor 8
    Threshold -1
    Memory Pool Manager Pages
    Reserved Current 0
    Reserved Limit 2095263
    Memory Pool (internal) Pages
    Allocations 464738
    Predicted 929941
    Private Target 0
    Private Limit 0
    Total Target 2560001
    Total Limit 2560001
    OOM Count 0
    MEMORYBROKER_FOR_CACHE (internal) Pages
    Allocations 14370
    Rate 1582
    Target Allocations 1646012
    Future Allocations 0
    Overall 2080000
    Last Notification 1
    MEMORYBROKER_FOR_STEAL (internal) Pages
    Allocations 409631
    Rate -242825
    Target Allocations 2039691
    Future Allocations 0
    Overall 2080000
    Last Notification 1
    MEMORYBROKER_FOR_RESERVE (internal) Pages
    Allocations 0
    Rate -59129
    Target Allocations 2080000
    Future Allocations 463125
    Overall 2080000
    Last Notification 1
    MEMORYBROKER_FOR_COMMITTED (internal) Pages
    Allocations 40735
    Rate 1
    Target Allocations 1670796
    Future Allocations 0
    Overall 2080000
    Last Notification 1
    MEMORYBROKER_FOR_XTP (internal) Pages
    Allocations 2
    Rate 0
    Target Allocations 1630062
    Future Allocations 0
    Overall 2080000
    Last Notification 1
    Memory Broker Clerk (Buffer Pool) Pages
    Total 274830
    Simulated 0
    Simulation Benefit 0
    Internal Benefit 0
    External Benefit 0
    Value Of Memory 0
    Periodic Freed 0
    Internal Freed 0
    Mainly we have SQL and IIS on server

Maybe you are looking for