Enabling SYS.MEMORYANALYTICS

Follow this procedure to enable the SYS.MEMORYANALYTICS virtual table.

Prerequisites


Procedure

Follow these steps to start a SQLFire member with the Java agent to provide memory analytics:
  1. Use the -javaagent:jar_path Java system property to specify the sqlfire.jar file in your installation when you start each SQLFire member. For example, if you use sqlf to start a SQLFire server:
    sqlf server start -client-address=1527 -J-javaagent:c:\vFabric_SQLFire_10x\lib\sqlfire.jar

    Specify the complete path and filename of sqlfire.jar for your system.

    If you use a locator for member discovery, also use the -javaagent:jar_path system property when starting the locator.

  2. If your schema and data are not already available in the SQLFire system (as persisted data), run any necessary SQL scripts to create the schema and load table data. For example:
    cd c:\vFabric_SQLFire_10x\quickstart
    sqlf
    sqlf> connect client 'localhost:1527';
    sqlf> run 'create_colocated_schema.sql';
    sqlf> run 'loadTables.sql';
  3. Connect to SQLFire and query the SYS.MEMORYANALYTICS table to view the memory usage information:
    sqlf
    sqlf> connect client 'localhost:1527';
    sqlf> select * from sys.memoryanalytics;
    SQLENTITY                
                   |ID                 
                                  |MEMORY
    ----------------------------------------------------------------
    APP.FLIGHTS (Entry Size, Value Size, Row Count)   
                   |dyozie-e4310(6880)<v0>:3439/59731
                                  |30352,31436,542
    
    AAP.FLIGHTS.DESTINDEX (Index Entry Overhead, SkipList Size, Max&
                   |dyozie-e4310(6880)<v0>:3439/59731
                                  |2104,696,3 (2803 = 2.74 kb)
    
    APP.FLIGHTS.DESTINDEX (Index Entry Size, Value Size, Row Count) 
                   |dyozie-e4310(6880)<v0>:3439/59731
                                  |4888,3784,87
    
    [...]