The GIP Prefilter - Usage Details

If the GIP prefilter is the default prefilter, any table you load is automatically configured for matching acceleration with the GIP prefilter at load time. If for any reason you do not wish a particular table to be so configured simply include the Boolean parameter LPAR_BOOL_GIPSEARCH with a value of false in the dbpars parameter list for the command lkt_dbload. The GIP prefilter must be created when the table is created, it cannot be added to or removed from an existing table.

Whenever database statistics are returned for a GIP prefilter enabled table, the value (LPAR_INT_DBIDXTOTALKBYTES) gives the total size of the GIP prefilter related data structures associated with this table.

Note: If predicate indexes also exist for the table this value also includes the space used by the predicate indexes (see Partition Indexes).

 

If the GIP prefilter is enabled for a table, by default searches on that table use the GIP prefilter. You can explicitly turn acceleration off for all tables by including the LPAR_BOOL_GIPSEARCH parameter with a value of false in the srchpars list you pass to lkt_dbsearch. This disabling of acceleration is effective for the current query only.

Whenever a lkt_dbsearch is done, the same Boolean parameter LPAR_BOOL_GIPSEARCH is returned in the stats list. This parameter is true if the GIP prefilter was employed, false otherwise.

If you are running Patterns Server on a Linux platform, and your hardware has qualified GPU units installed, you can configure your GIP prefilter to take advantage of the GPU processors to speed processing. See lkt_dbload command for a description of the related option arguments. For more information about GPU processing, see the TIBCO® Patterns Concepts Guide. For more information about enabling GPU processing when starting a server, see the TIBCO® Patterns Installation Guide.