1.1.1

For example, the following row from SYS.MEMORYANALYTICS shows that APP.FLIGHTS.DESTINDEX
uses 2803 bytes for skip lists:
SQLENTITY
|ID
|MEMORY
----------------------------------------------------------------
APP.FLIGHTS.DESTINDEX (Index Entry Overhead, SkipList Size, Max&
|dyozie-e4310(6880)<v0>:3439/59731
|2104,696,3 (2803 = 2.74 kb)
The second row for an index uses the SQLENTITY format: schema_name.table_name.index_name (Index Entry
Size, Value Size, Row Count). This row provides information similar to the values for a table entry. The ID
column value displays these values separated by commas:
DescriptionIndex Value
The per-index overhead, in bytes. (This includes the Index Entry
Overhead from the previous table, but excludes the Value Size
below.)
Index Entry Size
The size of the data structure used to point to the underlying region
entries, in bytes. For a unique index, this corresponds to the size of
a pointer reference.
Value Size
The total number of entries in the index.Row Count
For example, the following row from SYS.MEMORYANALYTICS shows that APP.FLIGHTS.DESTINDEX
has 4888 bytes of overhead with 87 index entries:
SQLENTITY
|ID
|MEMORY
----------------------------------------------------------------
APP.FLIGHTS.DESTINDEX (Index Entry Size, Value Size, Row Count)
|dyozie-e4310(6880)<v0>:3439/59731
|4888,3784,87
Displaying the Total Memory Footprint
You can query SYS.MEMORYANALYTICS with an optmizer hint to display the complete memory footprint
of tables and indexes.
Use the sizerHints=withMemoryFootPrint hint with your query to display the memory footprint:
SELECT * FROM sys.memoryAnalytics -- SQLFIRE-PROPERTIES
sizerHints=withMemoryFootPrint
;
Note: When processing a SQL script file, SQLFire does not recognize the terminating semicolon character
if it appears at the end of a SQL comment line. For this reason, you must place the terminating semicolon
on a separate line by itself, if the optmizer hint extends to the end of the statement.
When you include this optimizer hint, the query displays an additional row for each table and index, summarizing
the memory footprint for the SQLFire, GemFire, and other components. For example:
SQLENTITY
|ID
|MEMORY
----------------------------------------------------------------
[...]
vFabric SQLFire User's Guide76
Managing Your Data in vFabric SQLFire